Can’t change permissions – “The parameter is incorrect”

[Conn]

In this thread? No. I already stated that if I have more information, I'll post more information. Someone asked a question about the likelihood of it being in 4.2.16 because it's not in the beta, and I simply pointed out that the current public beta does not necessarily have every feature/fix slated to be in the final build.

You (or someone else) can't answer this?

Having the same problem. File permissions are a MESS, and seem to take ages to propergate. I'll make a file permission change, and nothing will happen until about an hour later - when I'll suddenly find it's decided to block all users.

Any update on this?

Grievous - an ETA would be nice, even if it's rough - and as asked by several users, what did you do to recreate this issue? If we know how you turned a working system, into a non-working system, then we may be able to work around this.
Many thanks.

[Grievous]

No, we don't give out every detail of our development and testing procedures.

Guys, look. I said I'd update the thread when I have more information. Getting hostile and jumping down my throat about things isn't going to get anything accomplished. If it keeps up I'll have to lock the thread, I'd rather not. Remember, I'm also an admin.

[Conn]

No, we don't give out every detail of our development and testing procedures.

Guys, look. I said I'd update the thread when I have more information. Getting hostile and jumping down my throat about things isn't going to get anything accomplished. If it keeps up I'll have to lock the thread, I'd rather not. Remember, I'm also an admin.

I think part of the issue is that when nothing is reported back on here, people assume this issue is not being looked at. Even posting on here every other week that you're still working on this would be helpful.

[Grievous]

It's simple, I'd rather post "I'll let you guys know in this thread when we have more information" than posting "nothing new yet" on a daily or weekly basis. Also, just because I haven't replied to each post on an individual basis, doesn't mean that I haven't been keeping up with posts in this thread, as I get an email every time someone replies, and I check the thread to see what it's about.

[sicabre]

Hi Grievous,

We understand what your are saying. I worked with some US and UK netgear engineers and i hope i found a workaround.
Now the UK engineer told me. Make new shares and set BASIC permissions and copy the folders over. Your NTFS permissions want be restricted but users can read/write/modify in it. THis is for the customer acceptable. MY customer is currently saying : Ok no problem, if the workaround is to make new shares and put basic permissions on in font vieuw and all users can access data. Then that's the workaournd.

Now that's what we are missing here. You are telling us that you will let us know when something will change. Now what do you think what we can say our customer who we promoted readynas? " Look customer, the readynas is a neat thing, but it has a bug. When we ask the developers of netgear they say; we know it's a issue but we haven't more information". It's all about communicating with us. We promoted netgear with several customers because it's really neat stuff. But this is not the way how to communicatie with us. Remember, people paid for functionality that doesn't work and we don't know if you addressing this issue.

We don't need all the details, but give us information so we can share it with customers so they know somebody is working on it. This customer now is really thinking about returning the readynas as i can't give him the information he wants. He's okay with the workaround but when is there a final resolution?

[Grievous]

I understand that, but if I don't have anything to communicate to you, you still don't have anything to tell the customer. Make sense? I could go to the extreme of posting every 5 minutes saying "We're still working on it but it's not done yet" but that doesn't accomplish anything either. If I don't have anything to tell you, I can't post anything. As I've said, when I have information I will post it, asking me to post info I don't have will not get either of us anywhere.

[jyarborough]

I guess the main theme here is that none of us want this issue to slip through the cracks. Speaking from my own perspective, this is the first time I have had to work with Netgear on an issue (our first ReadyNAS) and I don't have a high degree of trust built up yet that you guys will actually follow this through to resolution. The previous vendors we worked with (QNAP and Promise) also kept saying "we know it's a bug and we are working on it" for the quirky issues they had but I never saw resolution there after months of waiting (although they were pretty quick with a workaround in most cases) and eventually made the switch to Netgear. Now I am getting the same responses from Netgear. Do you have a bugzilla type site available so we can at least see that the bug is on the to-do list?

I really do not aim to offend you, Grievous, but I assume you are not the one actually fixing the problem. I assume you have relayed it to the developers and they are working on the issue, along with their many other feature requests, enhancements, bugs, etc. Sorry, but just taking your word for it doesn't do much for me (again, nothing personal).

[Grievous]

No, we do not have a public bugzilla type database. As far as who is working on it, more accurately would be "I'm not the only one working on the problem". Like I've said before, this isn't something that can be taken care of quickly and even after we've got a fix in place we still need to make sure it doesn't break something else.

[Grievous]

Ok, with the t-33 beta, we're only able to reproduce it with folders created prior to updating to t-33. Clearing the permissions on one of those folders and then re-creating them should work

[readynas_devotee]

Ok, with the t-33 beta, we're only able to reproduce it with folders created prior to updating to t-33. Clearing the permissions on one of those folders and then re-creating them should work

Thank you for the update Grievous. I applied t-33 to a brand new 6310-200 and I still receive the error message. PLEASE help - I have a $25k project on hold because of this.

Cheers.

[Grievous]

Ok, with the t-33 beta, we're only able to reproduce it with folders created prior to updating to t-33. Clearing the permissions on one of those folders and then re-creating them should work

Thank you for the update Grievous. I applied t-33 to a brand new 6310-200 and I still receive the error message. PLEASE help - I have a $25k project on hold because of this.

Cheers.

But is it happening with a NEW folder, or a folder that existed prior to updating to t-33?

[linenoise]

Going to give T-33 a shot I think.

While I'm waiting for about 6TB to copy I thought I'd mention that I noticed I'm getting errors from our XenServer backup script (which is mounting via CIFS for reasons unknown ) that are reporting:

Code: Select all

Error code: SR_BACKEND_FAILURE_44
Error parameters: , There is insufficient space,

This is strictly for new subfolders in a share that's been working fine until I upgraded to 4.2.15. Old directories are continuing to work perfectly. At the point the errors are thrown the script is attempting to export a snapshot to the ReadyNAS which has 2.75TB of free space available.

I doubt that's new info for you guys but it's marginally more illuminating than the errors Windows produce at least. I'll give it a go via NFS to once this backup run is finished.

[readynas_devotee]

But is it happening with a NEW folder, or a folder that existed prior to updating to t-33?

Hi Grievous,

Brand new out of the box. Had immediate issues with new shares and folders. Reset to factory. Tried again - failed.
Reset to factory. Updated to T-33.

New share, new folder. Fail. Tried resetting to factory after the first failure with same result.

I am happy to help, so let me know if you need anything.

Cheers.

rob

[perdahlstrom]

We also have this problem, and worse!
Running a ReadyNAS Pro (RAIDiator 4.2.15 ) with all users documents on it; Offline-files of My Documents-folder.
Server 2003 R2 AD-domain with mix of XP and Win7 clients.
Server 2003, Server 2003 R2, Server 2008 and Server 2008 R2 is available as member-servers.

All of a sudden users are locked out of randomly selected folders with "Access denied". Not necesarilly all folder, but some. When we try to fix this the error "Parameter is incorrect" occures, what ever we try to do on that users folder.
At the same time the other 40+ users are working fine, so it's not likely to be an error in the root-folder.

C:\USERS shared as "\\READYNAS\Users" in AD domain mode.
All users folders directly under this folder and "My Document" redirected to "\\READYNAS\USERS\%USERNAME%"

We have ACL like this;
USERS-folder (standard set by RAIDiator i think);
administrator - Full control - This folder, subfolders and fles
Users (READYNAS\Users) - Special - This folder only
nogroup (UNIX Group\nogroup) - Special - This folder only
Everyone - Special - This folder only
CREATOR OWNER - Special - Subfolder and files only
CREATOR GROUP - Special - Subfolder and files only
Everyone - Special - Subfolder and files only

On Sub-folders, named %USERNAME% (firtstname.lastname) we have;
Domain Admins - Full control - This folder, subfolders and fles
%USERNAME% - Full control - This folder, subfolders and fles
Everyone - None - This folder, subfolders and fles
CREATOR OWNER - Special - Subfolder and files only
CREATOR GROUP - Special - Subfolder and files only
administrator - Special - This folder only

BUT we have set ONLY Domain Admins and %USERNAME%, nothing else!

In some cases other users and groups appear in the ACL's without we adding them!
For exampel I have a "35926 (Unix Group\35926)" added in some users folders ACL's, and that is not anything I put in there! not even the user... Also "root (Unix User\root)" is set in some ACL's.

In some folder the "Domain Users" group appear, but I dont see a pattern that it is this group that are the error (sorry). Some folders work fin despite having it in ACL, still there is some folders that stop working and dont have it in ACL.

ReadyNAS messes with ACL's, that's for sure.
Problem is that it changes! If we set correct permissions and it works, we cannot trust it to work "forever".

As I type this I got two users that cannot create folders anywhere in their "My Documents" but can read them all fine. One other user has one folder (of many) that is unaccessible with error "Access denied".
...and I cannot do ANYTHING to fix it!

I as an domain admin get "parameter incorrect" when trying to change ACL or take ownership, "access denied" when trying to copy mentioned folder above.

FRUSTRATING!

/Per Dahlström, IT-consultant and Netgear Partner
MCSE with 20 years of experience of Windows Servers (NT3.5 - to date)

[Grievous]

perdahlstrom, that is not the same issue that we've been discussing in this thread. I would highly advise creating your own thread for this so we can keep it separate and avoid any confusion.