From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 84201] New: mount doesn't clear usrjquota / grpjqouta options
Date: Tue, 09 Sep 2014 14:28:52 +0000 [thread overview]
Message-ID: <bug-84201-13602@https.bugzilla.kernel.org/> (raw)
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@kernel-bugs.osdl.org
Reporter: robinedgar@gmail.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.
next reply other threads:[~2014-09-09 14:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 14:28 bugzilla-daemon [this message]
2014-09-10 13:48 ` [Bug 84201] mount doesn't clear usrjquota / grpjqouta options bugzilla-daemon
2014-09-11 6:00 ` bugzilla-daemon
2014-09-11 12:56 ` bugzilla-daemon
2014-09-11 13:10 ` bugzilla-daemon
2014-09-12 16:45 ` bugzilla-daemon
2014-09-12 16:47 ` bugzilla-daemon
2014-09-16 12:18 ` bugzilla-daemon
2014-09-16 20:23 ` bugzilla-daemon
2014-09-16 20:25 ` bugzilla-daemon
2014-09-18 10:04 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-84201-13602@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).