This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Please be more "professional" and elaborate on "because of quota concerns of other users". Otherwise, all sorts of rumor, myths and mis-information get spread, no?
If there is an issue/concern/bug/defect/etc you should be offer a bit more information to the public, so that we can assess the situation.
Some people have upgraded to 6.7, so where does that leave us?
You are a technology company, so it would be better to be more technical. And perhaps talks of "plans" as opposed to "hopes"
In ReadyNAS OS 6.4 we added quota support. This involved enabling quotas on the volume, regardless of whether quotas are set on any given share.
In 6.7.0 we added a GUI option to disable quotas at the volume level.
Unfortunately if share settings are changed quotas will be re-enabled on the volume still in 6.7.0. We've got a fix for this in the next release in 6.7.1.
A number of users that have updated to 6.7.0 have run into issues with quotas on the volume (users have. run into this on older firmware that uses quotas too, but it seems quite prevalent in early feedback from those users that have had problems on 6.7.0). As a workaround on 6.7.0 you can do an OS Re-install to disable quotas on the volume and consider deleting snapshots.
Volume quotas with large numbers of snapshots can lead to the NAS encountering an OOM (Out of Memory) condition. The NAS can only think about what it can hold in memory (RAM) and swap on the disks. If it runs out of RAM it will swap onto the disks and if it runs out of that as well, then the NAS will have to force shutting down services. If this doesn't resolve the problem very quickly this tends to lead to the system crashing.
OOM is caused by trying to run too much on a system at once e.g. due to running too many services & apps or a memory leak of some kind.
While most users should find the 6.7.0 update is a smooth one we weren't happy with the number running into problems so decided to pull the 6.7.0 release for now.
