"Read-only file system" Error // Permissions Problem

[Brosif_My_Nif]

I have been working on resolving this error for the past few weeks, but I've ran up against a wall. I have searched and tried some of the suggestions I thought may be applicable, but I am unable to resolve this error.

I am unable to change the permissions on one of my datasets ("PICTURES"). When I try to change the permissions via the GUI, I receive the following "Read-only file system" errors and it will not update the permissions for the dataset "PICTURES".

chown: /mnt/NAS_Volume2/PICTURES: Read-only file system
chmod: /mnt/NAS_Volume2/PICTURES: Read-only file system

If I copy a folder outside of the Read-only "PICTURES" dataset, I can then recursively change permissions via the GUI and regain access to that particular folder inside a new temporary dataset.

A few quick details:

• FreeNAS-9.10-STABLE-201604261518 (881b70d)
  
• CIFS settings are default
• Permissions Type set to "Unix" for all Datasets under Storage -> Volumes -> Change Permissions
• Mixed Windows & OSX Environment ... All permissions have been handled on the FreeNAS side and I have never experienced this kind of problem the past few years.
• This error started after I copied my datasets via "Replication Tasks" over to some new 8TB Reds I purchased to expand my pool.
• Fresh FreeNAS install

Shell Command "ls -lo" provides me with the following. I had to create a temporary dataset ("photography") because I am unable to write inside my normal "PICTURES" dataset where I currently have about 16TB of photos stored (both personal and business).

Please let me know if you have any suggestions I can try. I greatly appreciate any assistance you can offer.

If I am unable to resolve the problem, the next thing I was going to try is using the shell command "cp -R" to copy all my folders from the Read-only "PICTURES" dataset to the newly created "PHOTOGRAPHY" dataset where I have write privileges and then recursively changing the permissions via the GUI once everything is copied over. I hope I don't have to do that...

Thanks again in advance!

 

[dlavigne]

That sucks...

I know there were some changes to the replication system over the past few months and it sounds like the initial replication occurred when replicated datasets were being set to read-only. TBH, I'm not sure if that is still the behavior, and if it is, if that is desired, especially when restoring from a replicated dataset.

It might not hurt to create a bug at bugs.freenas.org that describes your current situation in order to get some dev feedback. If you decide to do so, post the issue number here.

 

[Brosif_My_Nif]

That sucks...

I know there were some changes to the replication system over the past few months and it sounds like the initial replication occurred when replicated datasets were being set to read-only. TBH, I'm not sure if that is still the behavior, and if it is, if that is desired, especially when restoring from a replicated dataset.

It might not hurt to create a bug at bugs.freenas.org that describes your current situation in order to get some dev feedback. If you decide to do so, post the issue number here.

Thank you, dlavigne. I have created a new bug report here: https://bugs.freenas.org/issues/15011

 

[Brosif_My_Nif]

Well, I got the answer I was looking for. I now have regained write access after the replication task. This really should be in the documentation. I would have never found this. I hope someone finds this thread in the future if they run into this problem.


From https://bugs.freenas.org/issues/15011:

FreeNAS is setting ZFS property readonly=on on datasets at destination side to prevent local changes and ensure uninterrupted flow of data from source to destination.

Fact that you've changed file permissions on destination dataset won't change ZFS dataset property value which is a totally different thing.

Go to shell and do:
zfs set readonly=off dataset_name