quota error

M

milan

Verified User
Joined
Dec 29, 2005
Messages
78
I am getting this error today when creating a user.

Details


Error with system Quotas
setquota: Device (/) filesystem is mounted on unsupported device type. Skipping. setquota: Mountpoint (or device) / not found. setquota: Not all specified mountpoints are using quota.

i did ran

cat /etc/fstab
Code: 
# /etc/fstab: static file system information.
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda1       /               ext3    defaults,errors=remount-ro 0       1
/dev/hda5       none            swap    sw              0       0
/dev/scd0       /media/cdrom0   iso9660 ro,user,noauto  0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
/               /               ext3    defaults,usrquota,grpquota 1       1
/home           /home           ext3    defaults,usrquota,grpquota 1       2dedi

it looks like /home is set good

/sbin/quotaoff -a
/bin/mount -o remount,rw /home
/bin/mount -o remount,rw /
/sbin/quotacheck -cavugm
/sbin/quotaon -a

these commands give me all this error:
quotaoff: Device (/) filesystem is mounted on unsupported device type. Skipping.

On the last reboot by the datacenter guy said to me that there was a problem mounting /home

Could that be a problem?
 
:rolleyes:

I need to get this fixed before this weekend but i dont know how. :confused:
 
Well, you've checked fstab but have you checked that your kernel supports it?

What operating system are you running?
What kernel version?
Has quota ever worked on this server? If so, what events occured shortly before it ceased functioning properly?
 
I am using a debian box. I dont know witch kernel it is running but i am getting this quota error since the last reboot. Before that it all was running ok.

I had to do this reboot becouse my server had been crached (locked down) After i assume a system backup I also installed kiss that day.
 
Last edited:
what does "2dedi" mean in the fstab entry for home?

Is that all there is, or did you leave something off the end in your cut and paste.

If you can't survive a reboot from a hack it means the hack was more successful than you'd like.

You should do a complete forensic study on your server; start by making sure there are no executable files in /tmp. In fact you should probably delete everything /tmp and reboot again.

If that doesn't work, then try changing the 2dedi (plus whatever's on the end of it to just the number 2, and see if you can mount the directory then.

Also try the mount command:
Code: 
# mount /home
and see if you get any better error message.

Jeff
 
Thanks for that comment. The 2dedi is there and I dont know what it does, ill check my tmp files and clear that dir.

I'll let you know how it goes.

Mounting give me this.

Code: 
dedi80:/# mount /home
[mntent]: warning: no final newline at the end of /etc/fstab
mount: /home is not a block device

I cleared tmp

Code: 
dedi80:/# rm -rf tmp/

The next problem is if i reboot the server will get down. Due some error with the startup. Might a kernel update fix this?
 
Last edited:
Personally, my guess is it's the fstab.
I would correct fstab (missed that 2dedi as it was off the screen) and restart. If it doesn't come back up, pop in your emergency boot disk.

If that doesn't fix it I would move on.

uname -a will show what kernel you're running.
 
Okey, I did that, 2.6.8-2-386 #1 Tue Aug 16 12:46:35 UTC 2005 i686 GNU/Linux

An other thing is, since i deleted /tmp my mysql is down. I recreated the directory but what premissions needs it to have.

The data center said to me the server hangs on boot at 2 fsck patities.

Code: 
e2fsck 1.37 (21-Mar-2005)
fsck.ext3: Is a directory while trying to open /home

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>
 
Last edited:
it seems i deleted the mysql.sock since it was in my /tmp map. :(

fixed it with
# mkdir tmp
# chmod 777 tmp
 
Last edited:
Hello,

Fyi, use 1777, and not 777 or else anyone can do anything to anyone elses files in /tmp (bad).

Also, this error is hinting that /home isn't an actual partition:

mount: /home is not a block device

Type "df -h" to show your list of actual partitions, and let us know if it exists or not.

For mysql, once /tmp is fixed up, run:
Code: 
killall -9 mysqld
killall -9 mysqld_safe
/etc/init.d/mysqld start
John
 
Okey I did chmod tmp to 1777

The results of 'df -h' is:

server1:/# df -h
Filesystem Size Used Avail Use% Mounted on
/ 73G 3.7G 66G 6% /
tmpfs 221M 0 221M 0% /dev/shm

Thank you for the support
 
ok, so based on that output, there is no /home partition (partitions and directories don't mean the same thing).

A partition is like an entire space of the hard disk reserved for a certain path. A directory doesn't have an entire portion of the disk reseved, it can show up anywhere on that partition.

Basically, you only have a / partition, not a /home partition. So your /home is just a directory that exists under /. Thus, you probably don't need the /home entry in your /etc/fstab file (unless you actually do but the syntax error is messing up the loading of /home). If /home works right now.. then you don't have a /home partition, so remove the /home line from your /etc/fstab file, it's not needed.

John
 
Okey I done that. But when I create a new user I am still getting thise message:

Code: 
An error has occurred

Details

Error with system Quotas
setquota:
Device (/) filesystem is mounted on unsupported device type. 
Skipping. setquota: Mountpoint (or device) / not found. setquota: 
Not all specified mountpoints are using quota.
 
Hello,

Is this a vps?
Also, type
Code: 
mount
to see what / is mounted as.
I'm guessing it's not of a type that supports system quotas.

What you can do, if you just want to hide that error, is run:
Code: 
cd /usr/sbin
mv setquota setquota.old
Then create a new setquota text file, and enter the following text into the file
Code: 
#!/bin/sh
exit 0;
The type "chmod 755 setquota" to make it executeable. That will suppress the error, and will not do anything when setquota is run.

John
 
Hey,

This is a dedicated box that I hire from the data center.

Code: 
server1:/# mount
/ on / type ext3 (rw,usrquota,grpquota)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)

Code: 
server1:/# cd /usr/sbin
server1:/usr/sbin# mv setquota setquota.old
server1:/usr/sbin# touch setquota
server1:/usr/sbin# pico setquota
server1:/usr/sbin# chmod 755 setquota
 
Actually, looking over the fstab file you posted, you've got 2 partition entires for / in it.. which isn't right. I think your fstab should be:
Code: 
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    defaults        0       0
/dev/hda1       /               ext3    defaults,usrquota,grpquota,errors=remount-ro 0       1
/dev/hda5       none            swap    sw              0       0
/dev/scd0       /media/cdrom0   iso9660 ro,user,noauto  0       0
/dev/fd0        /media/floppy0  auto    rw,user,noauto  0       0
Once that's set, run this to remount /:
Code: 
/bin/mount -o remount,rw /
Then use this guide to run quotacheck:
http://help.directadmin.com/item.php?id=42

John
 
Okey I edited fstab.

Code: 
server1:/usr/sbin# pico /etc/fstab
server1:/usr/sbin# cd ..
server1:/usr# cd sbin
server1:/usr/sbin# /bin/mount -o remount,rw /
mount: / not mounted already, or bad option
server1:/usr/sbin# cd ..
server1:/usr# cd ..
server1:/# /bin/mount -o remount,rw /
mount: / not mounted already, or bad option
server1:/# /usr/sbin/repquota quota_partition
repquota: Device (/) filesystem is mounted on unsupported device type. Skipping.
repquota: Can't stat() given mountpoint quota_partition: No such file or directory
Skipping...
repquota: No correct mountpoint specified.
repquota: Can't initialize mountpoint scan.
 
DirectAdmin Support said:
By "quota_partition", it means the quota partition, ie: /

/usr/sbin/repquota /

John
Click to expand...

Sorry i must have over looked that.
But when I use / it is giving me the same error.

Code: 
server1:/# /usr/sbin/repquota /
repquota: Device (/) filesystem is mounted on unsupported device type. Skipping.
repquota: Mountpoint (or device) / not found.
repquota: Not all specified mountpoints are using quota.
 
Ok, then it's not likeing this:

defaults,usrquota,grpquota,errors=remount-ro

Change it back to:

defaults,errors=remount-ro

in your /etc/fstab file. Looks like the kernel might not be able to handle quotas.

John
 
You must log in or register to reply here.
Back
Top