Release 4.1.9 - shares reverting to nobody/nogroup

[r0b]

If you have run into this issue please upgrade to 4.1.10: http://www.readynas.com/RAIDiator_4_1_10_Notes
You can then use the Advanced Options tab (go to Shares > Share Listing > Sharename then click on e.g. CIFS and you'll see the tab) to reset the ownership to what you want. You can use the Set ownership and permission for existing... option. Don't forget to click Apply to make your changes

My shares are set up so that they are read/write for owner, read-only for the 'users' group and no access for anyone else.

Since upgrading to the new 4.1.9 sparc firmware (http://www.readynas.com/?p=6480) the owner/group on the top level share directories keep reverting to nobody/nogroup as soon I change any share settings in FrontView.

Changing the 'Share folder owner' and 'Share folder group' in the 'Advanced Options' tab has no effect, they go back to nobody/nogroup the next time you go in. Even just adding a new share is enough to change the owner/group on the other shares back to nobody/nogroup.

At the moment I have to keep SSH'ing in and chmod/chgrp the directories back to what they should be.

4.1.8 was fine so this looks a problem with 4.1.9?

[Mr Yo]

Got exactly the same issue as described above since the Duo updated to release 4.1.9. I had to remove all read/write permissions to be able to access my protected shares.

[pugilares]

In the Frontview it's nobody/nogroup. But when I check folder properties from Windows Explorer (Win 7), then I see that files deeper within the share have proper owner.

I think I can see problem with Trash also. It's turned on in Frontview, but when I access from Windows 7 application and try to delete file, I get warning that the file will be deleted permanently because the volume doesn't support the trash.

[bmerle]

I have exactly the same issue since upgrading from 4.1.8 to the new 4.1.9 release ! In Frontview, it is just impossible to set any owner or group for any share (even newly created shares): it just keeps resetting to nobody/nogroup. The only way to access the files in the folder is to give permissions to everybody (not only the group, really everybody)... Help!

[melvsee]

Posting to say that I have the same problem. Giving access to everybody at the moment (and hoping nobody notices)

[techman05]

The advanced is for permissions and not security I thought. Aren't your, for example, cifs read/write permissions still setup? At least setup your users into groups so you can secure that way.

[sabljar]

Having the same issues here.

Can't set share folder group. Defaulting back to nogroup after the upgrade.

[smileymouse]

Reporting same issue here on NV+ share permissions all changed to nobody\nogroup with update to 4.1.9

Only the root folders have changed, all sub directories are okay. This of course means though I cannot create new subdirectorys, or delete them.

[arcticblue]

It would be good if this 'issue' could be officially confirmed by Netgear...

[rob@meerwijk.dk]

Same here, pretty annoying!

[lucs12]

Same here after "upgrading" my ReadyNAS Duo to 4.1.9.

Perhaps this issue also is responsible for the inability to access CIFS shares that many have experienced with 4.1.9: viewtopic.php?f=28&t=64322&p=360979#p360979. UPDATE: Indeed, after I changed, over SSH, the user and group of the share folders in /c from "nobody:nogroup" to myuser:mygroup, I could mount the shares in both MacOS and Linux. However, as soon as I open the "Advanced Options" tab for a share, the owner and group of the share are automatically changed to "nobody:nogroup" and I cannot access the share anymore. Rebooting the ReadyNAS also reverts the owner and group of a share to "nobody:nogroup".

[tryagain10]

I have the same problem!!!

Any solution yet?

[mdgm]

You can downgrade to 4.1.8 (http://www.readynas.com/RAIDiator_4_1_8_Notes) and use the Advanced Options tab to reset permissions should you wish to.

[audetto]

I have the same problem!!!

Any solution yet?

Same problem here.
My solution is to ssh into it and fix it.
But something must trigger it again, as I have already done it twice.

[Marcel-X]

Yep! Got the same problem after updating to the latest release!