From: Eric Sandeen <sandeen@redhat.com>
To: ext4 development <linux-ext4@vger.kernel.org>
Subject: can we simplify the quota matrix in ext4?
Date: Tue, 21 Jun 2011 13:45:50 -0500 [thread overview]
Message-ID: <4E00E6DE.9060208@redhat.com> (raw)
I was looking at
62d2b5f2dcd3707b070efb16bbfdf6947c38c194 ext4: Always journal quota file modifications
and was thinking - if we always journal, why do we still have all the mount options etc for journaled quota?
I guess without -o usrjquota=foo we don't journal right from mount time, and there are a few other paths that get skipped, but those seem like details...
It seems that ideally - and perhaps this is hindsight - ext4 should have defaulted to journaled, QFMT_VFS_V1 quotas only... is there any reason not to?
I'm still not very well versed in vfs quota, but does it seem possible to move in this direction? It seems odd that we should still be supporting unjournaled, vfsold-format quotas in ext4 these days. What's the point?
If it seems possible to move in this direction within the exiting quota framework I'd be interested in trying to get it done.
Thanks,
-Eric
next reply other threads:[~2011-06-21 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 18:45 Eric Sandeen [this message]
2011-06-21 19:24 ` can we simplify the quota matrix in ext4? Andreas Dilger
2011-06-22 6:35 ` Aditya Kali
2011-06-21 20:58 ` Eric Sandeen
2011-06-21 21:06 ` Andreas Dilger
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=4E00E6DE.9060208@redhat.com \
--to=sandeen@redhat.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