asubah
commented
1 year ago Dear Ammar, Thank you for reporting this issue.
The problem with our storage setup is that we are using Groups Quotas The group quotas set one quota for all the users in that group. This is not the required behaviour, what we want is to set a separate quota for each user. This can one be done through user quotas or directory quotas. So the only way to achieve the required behaviour is by using directory quotas.
Example:
- limit all users under /home/pg/ to 5GB
- limit all users under /home/ug/ to 2GB
- limit all users under /home/f/ to 10GB
Therefore, I had to delete all the quotas and set all users to 5GB limit for now until I have time to migrate the home directories to the new structure.
So I did the following login to isilon ssh admin_user_name@adhari_ip
After login, you will have access to isi command line tool that can be used
to administrate isilon
isi quota quotas list # see all quotas
isi quota quotas delete --all # delete all the existing quotas
# create a default-directory quota for all subdirectories
isi quota quotas create /ifs/data/adhari/zone1/nfs default-directory --enforced TRUE --hard-threshold 5GBIn case a user requires more data, we can easily unbind them from the rule through the GUI and set larger limit for them.
PS: quota command does not work with isilon :(
You can see your quota by running the following:
df /home/nfs/username -kh
Postgraduate student, facing a problem with account space trying to use Jupiter.
According to our quota assignments, postgraduate students should have 6GB. The student used 3.2 GB of the total space, which means the account still has 2.8 GB left, still, the message the student receives indicates that the account is running out of space.
When we tried to acquire quota information using the following command:
quota -v user_namewe get the following error as the below image shows:
keeping in mind that adhari is up and running, tested by pinging the server.