Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Sat, 2 Apr 2022 09:14:24 +1100
From:   Dave Chinner <david@fromorbit.com>
To:     wang.yi59@zte.com.cn
Cc:     djwong@kernel.org, linux-xfs@vger.kernel.org,
        linux-kernel@vger.kernel.org, xue.zhihong@zte.com.cn,
        wang.liang82@zte.com.cn, cheng.lin130@zte.com.cn
Subject: Re: [PATCH] xfs: getattr ignore blocks beyond eof
Message-ID: <20220401221424.GN1544202@dread.disaster.area>
References: <20220331212152.GG1544202@dread.disaster.area>
 <202204011609406223339@zte.com.cn>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <202204011609406223339@zte.com.cn>
Precedence: bulk

On Fri, Apr 01, 2022 at 04:09:40PM +0800, wang.yi59@zte.com.cn wrote:
> > On Thu, Mar 31, 2022 at 04:32:07PM +0800, wang.yi59@zte.com.cn wrote:
> > > > We do not, and have not ever tried to, hide allocation or block
> > > > usage artifacts from userspace because any application that depends
> > > > on specific block allocation patterns or accounting from the
> > > > filesystem is broken by design.
> > > >
> > > > If your application is dependent on block counts exactly matching
> > > > the file data space for waht ever reason, then what speculative
> > > > preallocation does is the least of your problems.
> > > >
> > >
> > > Thanks for your explaination.
> > >
> > > Unfortunately, the app I'm using evaluates diskusage by querying
> > > the changes of the backend filesystem (XFS) file before and after
> > > the operation.
> >
> > What application is this?
> >
> > What is it trying to use this information for?
> 
> Thanks very much, Dave.
> 
> I'm trying to use a new xlater(module) named 'simple-quota' in
> glusterfs, which collects file's diskusage by stat, for quota function.

So a company (kadalu) has forked gluster, then removed the gluster
quota implementation because of undefined "major performance
problems" and then implemented their own quota thing that stores
disk usage information in extended attributes. And:

	Advised method is adding quota limit info before writing any
	information to directory. Even otherwise we don’t need quota
	crawl for updating quota-limit, but do a du -s -b $dir and
	write the output into xattr.

Yeah, that's broken by design.

Oh, look at that:

	Just run statfs() on all dirs which has Quota set, and send
	a flag to update status of quota xlator through internal
	xattr mechanism if quota limit exceeds for a directory! This
	can run once in 5 or 10 seconds, or even lesser frequency if
	the quota limit is huge!

That's pretty broken, too. Doesn't scale out, either...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com