From: Nicole Skyrca (nskyrca@syr.edu)
Date: Mon Mar 01 2004 - 11:45:10 EST
Hello,
I've recently had a situation where a user reported that when they ran the
command
"quota -v username", they recieved the headers to the output, but no disk
usage information.
Upon further investigation, I found that some users in this filesystem had
quotas set,
and others did not, but they all are supposed to have quotas set. The
commands repquota
and quotacheck both would hang after showing some user information. When
running
the command "ls -al" on the quotas file on a machine where the directory was
NFS mounted,
I got the output "File too large". Running this command on the fileserver
showed the the file
contained 10655731520 bytes, while the quotas file on another filesystems was
only 32822112
bytes.
I assumed that the quotas file must be corrupt, so I moved the quotas file to
another name, and
recreated all (8000) user quotas on that filesystem from scratch. The
repquota and quotacheck
commands no longer hang, and things on that filesystem seem to be working as
expected now.
Does anyone currently (or have any suggestions on how to) monitor disk quotas
to verify they
are working properly and that the quotas file isn't corrupt? My only idea is
to write a script to run
quotacheck or repquota periodically, but I'm not sure how to check if the
commands are hanging,
or logging the correct information. Any ideas on how the quotas file became
corrupt and how I could
prevent it from happening again?
Thanks,
Nicole
Nicole Skyrca
Syracuse University
Computing and Media Services
Machinery Hall
315-443-5310
nskyrca@syr.edu
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:28:09 EDT