linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-fsdevel@vger.kernel.org, swhiteho@redhat.com,
	xfs@oss.sgi.com
Subject: Re: [PATCH 00/10] quotactl fixed and cleanups
Date: Tue, 16 Feb 2010 16:54:38 -0500	[thread overview]
Message-ID: <20100216215438.GA23628@infradead.org> (raw)
In-Reply-To: <20100216212634.GI3153@quack.suse.cz>

On Tue, Feb 16, 2010 at 10:26:34PM +0100, Jan Kara wrote:
>   The semantics I've chosen for OCFS2 is that if "USRQUOTA" filesystem
> feature is enabled, we always do accounting of users' usage (as this is
> essntially filesystem metadata). 'usrquota' mount option is just ignored
> and used only to make life easier to quota-tools (so that they don't have
> to parse superblock to find whether quota is supported or not). Enforcement
> is enabled / disabled by quotactl call.
>   I'd eventually love to convert ext3/4 to this behavior as well (and move
> quota files to be invisible "system" inodes) so if XFS would be consistent
> with this, it would be nice.

XFS is almost but not quite consistant with that.  XFS has mount
options for accounting and enforcement, but no superblock bit yet.
Accounting always needs to be enabled at mount time, and enforcement
can be enabled/disabled with quotactl / xfs_quota in addition to the
mount option.  We have been thinking about optionally also adding the
superblock flag as that would make a lof of things easier, especially
for quotas on the root filesystem.


  reply	other threads:[~2010-02-16 21:54 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-16  8:44 [PATCH 00/10] quotactl fixed and cleanups Christoph Hellwig
2010-02-16  8:44 ` [PATCH 01/10] quota: split do_quotactl Christoph Hellwig
2010-02-16  8:44 ` [PATCH 02/10] quota: clean up checks for supported quota methods Christoph Hellwig
2010-02-16  8:44 ` [PATCH 03/10] quota: special case Q_SYNC without device name Christoph Hellwig
2010-02-16  8:44 ` [PATCH 04/10] quota: simplify permission checking Christoph Hellwig
2010-02-16  8:44 ` [PATCH 05/10] quota: clean up Q_XQUOTASYNC Christoph Hellwig
2010-02-16  8:44 ` [PATCH 06/10] quota: move code from sync_quota_sb into vfs_quota_sync Christoph Hellwig
2010-02-16  8:44 ` [PATCH 07/10] quota: remove invalid optimization from quota_sync_all Christoph Hellwig
2010-02-16  8:44 ` [PATCH 08/10] quota: split out netlink notification support from quota.c Christoph Hellwig
2010-02-16  8:44 ` [PATCH 09/10] quota: split out compat_sys_quotactl " Christoph Hellwig
2010-02-16  8:44 ` [PATCH 10/10] quota: drop permission checks from xfs_fs_set_xstate/xfs_fs_set_xquota Christoph Hellwig
2010-02-16  8:48 ` [PATCH 00/10] quotactl fixed and cleanups Christoph Hellwig
2010-02-16 10:37 ` Steven Whitehouse
2010-02-16 18:36 ` Jan Kara
2010-02-16 19:12   ` Christoph Hellwig
2010-02-16 21:26     ` Jan Kara
2010-02-16 21:54       ` Christoph Hellwig [this message]
2010-02-17 19:37   ` Christoph Hellwig
2010-02-17 23:34     ` Jan Kara
2010-02-25 22:04 ` Alex Elder

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=20100216215438.GA23628@infradead.org \
    --to=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=swhiteho@redhat.com \
    --cc=xfs@oss.sgi.com \
    /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).