Unable to change "share folder group" FIXED in 4.1.10 [T3]

[mgferg]

Hi,

I've been having these issues also - been drving me nuts! Above 4.1.10 beta fixed it.

Regards,

Mark

[AlecEdworthy]

Can you try 4.1.10 beta?: http://www.readynas.com/forum/viewtopic.php?f=17&t=59222

Thanks, I'm downloading it now and will have a go at installing it soon.

Kind regards, Alec

[mdgm]

Tried it myself earlier today and the fix works for me. After the update to 4.1.10-T3 affected shares have their ownership changed to nobody:nogroup from root:nogroup. 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 and this works and survives a reboot.

[arcticblue]

Tried it myself earlier today and the fix works for me. After the update to 4.1.10-T3 affected shares have their ownership changed to nobody:nogroup from root:nogroup. 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 and this works and survives a reboot.

What does 'affected shares' mean exactly? If i were to upgrade to 4.1.10 will my shares be changed/modified/altered in any way (given that i would comes from 4.1.9-T10)?

[mdgm]

An affected share would be one that you've had the ownership/permissions problems on, the root folder (e.g. "media" folder for the "media" share) would have it's ownership changed to nobody:nogroup. The files would still be there and intact.

[arcticblue]

An affected share would be one that you've had the ownership/permissions problems on, the root folder (e.g. "media" folder for the "media" share) would have it's ownership changed to nobody:nogroup. The files would still be there and intact.

Thx for the quick reply!

Let's see if I understand this correctly.
The issue discussed here has been mentioned several times throughout the betas, and seemingly introduced on larger scale with the 4.1.9 release.
If no symptoms have appeared, the 4.1.10-T3 release would do nothing on existing shares and its current ownership/permissions, right?
For those shares with symptoms, the ownership/permissions will be reverted to nobody:nogroup, allowing for the appropriate changes/modifications via the web GUI, right?

I guess I miss a full description as of what was fixed and if ANY action is needed to get back on track again (regardless from where I am firmware wise, and regardless if I experience problems with shares or not)...
I have been sitting still with 4.1.9-T10 and would like to move along... can that be safely done now or should one wait until the official 4.1.10 release?

[mdgm]

If your shares don't have problems nothing would be done to them. However you do appear to be running an affected firmware. I'd go ahead with the update.

[AlecEdworthy]

I applied the update last night and everything seemed to go smoothly and I can now update the ownerships again (well the group at least, I didn't try the user).

Thanks to all concerned

Alec

[arcticblue]

Upgraded from 4.1.9-T10 to 4.1.10-T3 and everything seems to work as expected
File access seems quicker as well (subjectively based).

[mdgm]

4.1.10 is now available: http://www.readynas.com/RAIDiator_4_1_10_Notes