[BusyBox 0000988]: mount does not support usrquota/grpquota options

bugs at busybox.net bugs at busybox.net
Tue Aug 8 11:53:18 UTC 2006


The following issue has been SUBMITTED. 
====================================================================== 
http://busybox.net/bugs/view.php?id=988 
====================================================================== 
Reported By:                massaware
Assigned To:                BusyBox
====================================================================== 
Project:                    BusyBox
Issue ID:                   988
Category:                   Other
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
====================================================================== 
Date Submitted:             08-08-2006 04:53 PDT
Last Modified:              08-08-2006 04:53 PDT
====================================================================== 
Summary:                    mount does not support usrquota/grpquota options
Description: 
we are trying to get quota working on a reiserfs filesystem created on an
md raid device /dev/md0. However, when issuing a mount command to mount
the device with the usrquota/grpquota options, the following error message
is returned:

mount /dev/md0
mount: Mounting /dev/md0 on /mnt/data failed: Invalid argument

this when using the following fstab entry:

/dev/md0   /mnt/data    reiserfs  usrquota,grpquota,noauto,noatime       
1 2

when mounting without using fstab but by forcing the options on
commandline, the command succeeds:

~ # mount -t reiserfs -o usrquota,grpquota,noatime /dev/md0 /mnt/data
~ # mount
/dev/md0 on /mnt/data type reiserfs (rw,noatime)

~ # quotaon -vug /mnt/data
/dev/md0 [/mnt/data]: group quotas turned on
/dev/md0 [/mnt/data]: user quotas turned on

HOWEVER, quotas aren't really enabled, users can do whatever they want
with the drive, no limits is imposed.

When using util-linux's mount, everything works without any problems, by
using the same commands as stated above, so this has to be an issue with
busybox's mount.
====================================================================== 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-08-06 04:53  massaware      New Issue                                    
08-08-06 04:53  massaware      Status                   new => assigned     
08-08-06 04:53  massaware      Assigned To               => BusyBox         
======================================================================




More information about the busybox-cvs mailing list