xfs
[Top] [All Lists]

Re: 3.5.0-rc5: inconsistent lock state

To: Dave Chinner <david@xxxxxxxxxxxxx>
Subject: Re: 3.5.0-rc5: inconsistent lock state
From: Christian Kujau <lists@xxxxxxxxxxxxxxx>
Date: Thu, 5 Jul 2012 16:39:21 -0700 (PDT)
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to: <20120705215940.GP19223@dastard>
References: <alpine.DEB.2.01.1207041206390.5568@xxxxxxxxxxxxxx> <20120705074307.GA28127@xxxxxxxxxxxxx> <alpine.DEB.2.01.1207050535420.5568@xxxxxxxxxxxxxx> <20120705215940.GP19223@dastard>
User-agent: Alpine 2.01 (DEB 1266 2009-07-14)
On Fri, 6 Jul 2012 at 07:59, Dave Chinner wrote:
> It means that you have enough attributes that they don't fit in the
> inode, so every time they are read or written you have to do an
> extra IO on top of reading/writing the inode. Performance can easily
> drop by an order of magnitude when the attributes are moved out of
> the inode....

xfs_info shows isize=256 - but I'm not sure how I would have exceeded that 
limit? I'm not using SELinux or anhy other security frameworks on that 
machine, only plain unix permissions. Just check again, no ACLs, no EAs, 
no file attributes are set on these filesystems.

The filesystems make heavy use of hardlinks, but files usually have no
more than ~12 hardlinks, so that counter should not exceed the inode
size either.

> Typically there is 50-70 bytes of attribute space available in 256
> byte inodes, larger attributes or lots of them will push them out of
> the inode....

50 bytes sounds more than enought for holding only unix permissions. Does 
it matter that the filesystem is somewhat larger? Not too large though, 
all xfs filesystems are < 1TB in size.

Thanks,
Christian.
-- 
BOFH excuse #211:

Lightning strikes.

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