[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Tue, 09 Sep 2014 14:28:52 +0000
From: bugzilla-daemon@...zilla.kernel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 84201] New: mount doesn't clear usrjquota / grpjqouta options
https://bugzilla.kernel.org/show_bug.cgi?id=84201
Bug ID: 84201
Summary: mount doesn't clear usrjquota / grpjqouta options
Product: File System
Version: 2.5
Kernel Version: 3.2.0-4-amd64
Hardware: i386
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: ext4
Assignee: fs_ext4@...nel-bugs.osdl.org
Reporter: robinedgar@...il.com
Regression: No
Hi, After changing the group quota file name in after the first run of
remount -o remount /
gives a
mount: / not mounted or bad option
error.
If you remove the usrjquota and groupjquota options from the fstab and remount,
mount runs. dmesg gives
EXT4-fs (vda1): re-mounted. Opts: (null)
but when you
mount
it still shows the old usrjquota and groupjquota values in the output.
/dev/disk/by-uuid/2ceaad1e-7ca8-42f9-b657-ce689beba638 on / type ext4
(rw,relatime,errors=remount-ro,user_xattr,barrier=1,data=ordered,jqfmt=vfsv1,usrjquota=aquota.user,grpjquota=aquota.user)
The same if you specify the noquota option in fstab or options. dmesg then
gives
EXT4-fs (vda1): re-mounted. Opts: noquota
If you remove all from the fstab and try
mount -o
remount,usrjquota=aquota.user,grpjquota=aquota.otherfilename,jqfmt=vfsv1 /
You get the bad option error again. In dmesg you get
EXT4-fs (vda1): group quota file already specified
I have deleted the old files and made sure that quotas are off using
quotaoff -afugpv
How do you clear the options completely?
--
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists