Still there are problems with filesystem with quota enabled, and it's quite 
strange because "quota" is one of the mostly used feature on any server!
If SysAdmin does not modify /etc/rc.d/rc.sysinit by hand, there's always an 
error message: filesystem is busy etc. etc.
It's not a disaster, I just have to comment some lines in rc.sysinit and 
everything works nice. But in Redhat it does not happen: since first reboot 
if "usrquota,grpquota" is detected and quotacheck is run, all goes fine.
It would be really nice to solve this matter: for example
- Put "usrquota" and "grpquota" between filesystem options into the installer
- If "usrquota" and/or "grpquota" is detected in fstab, just run
        quotacheck -vm[g,u] <filesystem>
or simply
        quotacheck -avug <filesystem>
so if aquota.* is not present, it's generated and no error message should be 
given anymore.
- If the files aquota.user and/or aquota.group is detected, do nothing or 
just perform a consistency check.
- Don't try to "quotacheck" with strange options on mounted filesystems!

Thanks in advance,
Claudio

-- 
Claudio Panichi, System/Network Admin at Dept. of Physics
"Tor Vergata" University and INFN - Sec. "Roma II"
Remote System is: LINUX!

Reply via email to