From: Ted Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: Aditya Kali <adityakali@google.com>,
adilger@dilger.ca, dmonakhov@openvz.org,
linux-ext4@vger.kernel.org
Subject: Re: Support for ext4 hidden quota inodes in quota-tools
Date: Tue, 22 Nov 2011 18:51:53 -0500 [thread overview]
Message-ID: <20111122235153.GA5167@thunk.org> (raw)
In-Reply-To: <20111122201206.GA5029@quack.suse.cz>
On Tue, Nov 22, 2011 at 09:12:06PM +0100, Jan Kara wrote:
>
> this is just a heads up that I've modified quota tools to handle
> quota files in hidden inodes for ext4. Current source code can be pulled
> from git repository at sf.net: linuxquota.git.sourceforge.net
Could you give a quick summary of what the functionality the quota
tools will have vis-a-vis the hidden inodes? I assume things like
repquota will work. But will quotacheck work? Quite frankly I'd much
rather it didn't since then it might get confusing since some people
might try to do the evil thing of running quota check on a live file
system, with all of the races that might imply, versus using e2fsck to
check and update the quota files as part of the fsck process.
Also, I had hoped to have the model where quota tracking would be
enabled automatically when the file system was mounted, and there
would not be a way of disabling quota tracking except when the file
system was unmounted, so at least in theory the only way the quota
files could get stale is if the file system was corrupted or modified
directly via tools like e2tools or debugfs. Presumably we'll be able
to enforce this by having the kernel refuse the quotaoff quotactl
request, but I just want to make sure the overall user experience
between the kernel support, the e2fsprogs support, and the quota tools
all come together in a way that's optimal for the sysadmin who will
need to use all of this stuff.
Cheers,
- Ted
next prev parent reply other threads:[~2011-11-22 23:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-22 20:12 Support for ext4 hidden quota inodes in quota-tools Jan Kara
2011-11-22 23:51 ` Ted Ts'o [this message]
2011-11-23 11:32 ` Jan Kara
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=20111122235153.GA5167@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=adityakali@google.com \
--cc=dmonakhov@openvz.org \
--cc=jack@suse.cz \
--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