xfs
[Top] [All Lists]

Re: [PATCH 00/10] quotactl fixed and cleanups

To: Jan Kara <jack@xxxxxxx>
Subject: Re: [PATCH 00/10] quotactl fixed and cleanups
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Tue, 16 Feb 2010 16:54:38 -0500
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-fsdevel@xxxxxxxxxxxxxxx, swhiteho@xxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <20100216212634.GI3153@xxxxxxxxxxxxx>
References: <20100216084446.377980079@xxxxxxxxxxxxxxxxxxxxxx> <20100216183627.GC3153@xxxxxxxxxxxxx> <20100216191207.GA3856@xxxxxxxxxxxxx> <20100216212634.GI3153@xxxxxxxxxxxxx>
User-agent: Mutt/1.5.19 (2009-01-05)
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.

<Prev in Thread] Current Thread [Next in Thread>