BTRFS command to change disk to RW

[Stevek (Steve Kaufman)]

I have a directory snapshot that I can not get to stay mounted and it gos RO all the time.
@Hooverdan I think it was you that gave me a command to change it to RW. Could you supply again.
I caused this trying to cleanup replication files.

        Traceback (most recent call last):

File “/opt/rockstor/src/rockstor/storageadmin/views/share.py”, line 379, in delete
remove_share(share.pool, share.subvol_name, share.pqgroup, force=force)
File “/opt/rockstor/src/rockstor/fs/btrfs.py”, line 1185, in remove_share
toggle_path_rw(subvol_mnt_pt, rw=True)
File “/opt/rockstor/src/rockstor/system/osi.py”, line 546, in toggle_path_rw
return run_command([CHATTR, attr, path])
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/opt/rockstor/src/rockstor/system/osi.py”, line 289, in run_command
raise CommandException(cmd, out, err, rc)
system.exceptions.CommandException: Error running a command. cmd = /usr/bin/chattr -i /mnt2/Data-2/.snapshots/c0450590-f2b9-de11-8a1b-90e6ba7a072b_Documents-11/Documents-11_2_replication_1. rc = 1. stdout = [‘’]. stderr = [‘/usr/bin/chattr: Read-only file system while setting flags on /mnt2/Data-2/.snapshots/c0450590-f2b9-de11-8a1b-90e6ba7a072b_Documents-11/Documents-11_2_replication_1’, ‘’]

[Hooverdan (Dan W.)]

Are you referring to this post?

Disk structure under /mnt2 and replication question

to ensure that there wasn’t any quota processing getting in the way, I recreated the scenario but this time on the receiving system I disabled quotas at the pool level. Did not seem to make a difference. it still failed at the fourth replication with the same error message on the receiving system: [17/Sep/2024 13:55:02] INFO [storageadmin.views.snapshot:61] Supplanting share (6f32cb58-f849-4c93-bc65-6ebda422c66d_Replication) with snapshot (.snapshots/6f32cb58-f849-4c93-bc65-6ebda422c66d_Replic…

The command line was:

/usr/sbin/btrfs property set -f <path to mounted share> ro false

Here I successfully added it to the btrfs.py file:

Disk structure under /mnt2 and replication question

Thanks for providing your thoughts on this. I did notice that difference, but assumed that, while a symptom of something not working, it wasn’t at the core of failure after the third replication (or at least I think so). I added the force flag in btrfs.py on the receiver side here: def set_property(mnt_pt, name, val, mount=True): if mount is not True or is_mounted(mnt_pt): cmd = [BTRFS, "property", "set", mnt_pt, name, val] return run_command(cmd) like this: def set_prop…

which was then resolved via this PR:

replication received_uuid blocker re snap to share promotion

and became available with version 5.0.15-0

[Stevek (Steve Kaufman)]

@Hooverdan

/usr/sbin/btrfs property set -f <path to mounted share> ro false

Yes Thx so much I could not find it.