Read-only file system, unable to write anything after replication

I have a problem with this procedure, I moved my datas to another pool of disks and I am sure I have checked that the “Set destination in read-only mode” checked was not checked, but some datasets in the batch has been set to read only mode.

I tried to get to the ACL window but when I hit “Save” i get the following error :

Erreur: setacl

/mnt//: dataset underlying path has the readonly property enabled.

I can’t find a way to remove that ReadOnly rule

I found this thread on the old forum

But the command zfs set readonly=off tank/my_data returns zsh: command not found: zfs on my system.

Is there another way of setting my datasets back to normal or did I missed something ?

Thank you in advance

If running SCALE, prefix zfs with sudo.
But it would be best to remove the flag from GUI.

Thank you, It worked ?
but isn’t the answer to a sudo command where “sudo” is missing supposed to be “this needs sudo” ?

Is there any way to make this recursive (for all subdatasets) ?

Without sudo, the command is not found in $PATH.

Use the recursive flag, or, better, the GUI.

Thanks for the explanation.
Just for the record, where in the GUI is this supposed to be found ? (I would not have ended up here if I found it)

Looking up on 25.04…
Datasets > Edit > Advanced options > Read-only drop-down in the (lenghty) scroll-down list. I admit that it’s somewhat less obvious than in CORE.

1 Like