From: Ted Ts'o <tytso@mit.edu>
To: Johann Lombardi <johann@whamcloud.com>
Cc: Aditya Kali <adityakali@google.com>, linux-ext4@vger.kernel.org
Subject: Re: quotacheck on 'tune2fs -O quota'
Date: Mon, 7 Nov 2011 16:28:25 -0500 [thread overview]
Message-ID: <20111107212825.GI24234@thunk.org> (raw)
In-Reply-To: <20111107203836.GB3191@granier.hd.free.fr>
On Mon, Nov 07, 2011 at 09:38:36PM +0100, Johann Lombardi wrote:
> > I agree it would be useful to allow upgrades using existing quota
> > files. I just didn't have a way of doing this correctly though so I
> > had removed it. But this patch fixes it, so I am all for including it.
>
> Great, thanks.
It's more than useful, it's mandatory. It wasn't important for
Aditya's application since he was mainly worried about tracking disk
space usage. But for anyone who cares about doing quota enforcement,
losing the quota limits when you ran e2fsck is a non-starter.
Just to get this on record, since we discussed this on the weekly
conference call. I'm currently planning on making quota disabled by
default in e2fsprogs, so that anyone who wants to use quota will have
to use an --enable-quota configure option. That's because I'm not
completely convinced that quota is fully baked and tested. After
reviewing Niu's patches, I'll apply them, and that way the quota
feature won't hold up the e2fsprogs 1.42 release. People who feel
comfortable using it can enable it via --enable-quota, and after we
give it a bit more of a shakedown, we can enable it by default in some
1.42.X maintenance release.
Thanks to Niu and whamcloud for implementing this critically needed
bit of functionality!
- Ted
next prev parent reply other threads:[~2011-11-07 21:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 5:20 quotacheck on 'tune2fs -O quota' Niu
2011-11-04 0:13 ` Aditya Kali
2011-11-04 9:03 ` Johann Lombardi
[not found] ` <CAGr1F2FQ=MAqd8NiamZ39K9dX8YC_JiaUszFod3tG=CK+W0GGQ@mail.gmail.com>
2011-11-07 20:38 ` Johann Lombardi
2011-11-07 21:28 ` Ted Ts'o [this message]
2011-11-07 21:56 ` Aditya Kali
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=20111107212825.GI24234@thunk.org \
--to=tytso@mit.edu \
--cc=adityakali@google.com \
--cc=johann@whamcloud.com \
--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