I have a ReadyNAS 4200 device and after looking into setting up disk quotas on Home/user folders I added a 30gb limit to an AD user group, however some of our developers were part of that group and can no longer upload files to our development share. So I removed the quota from the group but that made no difference, so I rebooted the device but still no luck.
I need to allow our developers access to these shares with out getting a disk full error (we have 7TB available on the device). It has to be something to do with the quotas as whenever someone tries to write to the folder I get a warning from the NAS box stating that a user has gone over the limit. ALL quotas on users and groups now read 0 so I am either missing something obvious or the quota hasn't been removed.
the error I get is:
Disk block limit reached on volume C for user 'dean.wheatley'.
Disk space used: 178 GB (Limits: 31 GB soft, 39 GB hard) User 'dean.wheatley' is now prevented from using additional disk space.
Thanks for the reply.. I did the reboot with the quota check option checked under 4.2.22, but that changed nothing
Is there a significant difference to update from 4.2.22 to 4.2.24?, ie Is this quota issue a know problem and 4.2.24 will fix it? as I am reluctant to run the update in case there are other adverse effects
I have also noticed there are 2 files in the root of c when viewing the shares from a domain admin account. aquota and aquota.user, seems likely that these could be a cause?, If I deleted them is it likely to cause other problems?
It is normal for aquota and aquota.user to be present on the c volume - even if you have no quotas set. I'm not sure what would happen if you deleted them.
Have you confirmed that there is neither a quota for the user nor the group?
When you rebooted to do the quota check did you select to do a volume scan as well? if so, try it again but this time only select to do a quota check.
What web browser and version did you use to set the quotas? Note that 4.2.23 added compatibility with IE10. I'm not sure if there was a compatibility issue with setting quotas though.
If you like you could contact tech support and if all else fails they could remotely login to the unit to fix the quotas.
I have been through the security > user & group accounts and rechecked the lists using Chrome and IE and both show 0 under the Quota column for all users and groups. When I did the reboot I selected shutdown and reboot and check and fix quotas on next boot options, I did not perform the volume scan as it did not seem relevant to the issue. I used Chrome to set the quotas and to remove them when the issue started to appear. We don't have a tech support contract 😞
Very odd, after refreshing the UIDs in the user list, the quota I had previously removed popped back in against 1 user name. Removed the quota again and it fixed the issue. What is puzzling is that the other users who experienced this issue were using their own username, which had NEVER had a quota set against them. So how can setting a quota on one user effect everyone else?
