Weird quotas problem

vivalafe

Verified User
Joined
Jul 17, 2005
Messages
42
Location
Santo Domingo
Hello,

I Installed a new server with CentOS 5.2 64 bits. DirectAdmin was installed and everything works fine except for the quotas.
When I create a new user in Directadmin system shows a "Error with system Quotas / setquota: Quota file not found or has wrong format. setquota: Not all specified mountpoints are using quota." A similar error appears with command line commands like repquota. Quotaoff or quotaon commands brings a "Cannot find quota file on /home [/dev/sda6] to turn quotas on/off."

If I try to create the quota file with quotacheck, then I get the following:

[root@vn1126 conf]# /sbin/quotaoff -a; /sbin/quotacheck -avugm; /sbin/quotaon -a;
quotaoff: Cannot find quota file on /home [/dev/sda6] to turn quotas on/off.
quotaoff: Cannot find quota file on /home [/dev/sda6] to turn quotas on/off.
quotacheck: Scanning /dev/sda2 [/] done
quotacheck: Checked 10291 directories and 128268 files
quotacheck: Scanning /dev/sda6 [/home] quotacheck: Something weird happened while scanning. Error 2133571361
quotaon: Cannot find quota file on /home [/dev/sda6] to turn quotas on/off.
quotaon: Cannot find quota file on /home [/dev/sda6] to turn quotas on/off.

The same happened with quotacheck -cug command parameters.

My /etc/fstab shows the following:

LABEL=/ / ext3 defaults,usrquota,grpquota 1 1
LABEL=/home /home ext3 rw,usrquota,grpquota 1 2
LABEL=/boot /boot ext3 defaults 1 2
tmpfs /dev/shm tmpfs defaults 0 0
devpts /dev/pts devpts gid=5,mode=620 0 0
sysfs /sys sysfs defaults 0 0
proc /proc proc defaults 0 0
LABEL=SWAP-sda3 swap swap defaults 0 0
LABEL=SWAP-sda5 swap swap defaults 0 0

Any ideas to solve this problem??

Thanks in advance.
 
Problem solved

It was a hard disk failure issue.
Once disk was replaced and system and DA reinstalled, quotas work perfectly.

Maybe this error can warn other users about a possible hard drive failover coming soon:

"quotacheck: Something weird happened while scanning. Error 2133571361"
In this case, checking the /var/log/messages for disk read or write errors can be a good idea.

Thanks for the reply.
 
Last edited:
Back
Top