Re: 3.5.0-rc5: inconsistent lock state

[Dave Chinner <david@fromorbit.com>]

On Thu, Jul 05, 2012 at 05:44:50AM -0700, Christian Kujau wrote:
> On Thu, 5 Jul 2012 at 03:43, Christoph Hellwig wrote:
> > See my "do not take the iolock in inode reclaim context" series from
> > yesterday, which should take care of this.
> 
> OK, good. I'll wait until this hits mainline then.
> 
> > Btw, if you hit this it's a sign you have out of the inode attributes,
> > so if this isn't just a single inode with them you might be better off
> > using larger inodes.
> 
> ..."(run) out of inode attributes" - not really sure what that means and 
> why that would be the case.

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....

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....

> And "using larger inodes" sounds like a 
> reformat with a larger "-i size=" option.

Yes, inode size is defined at mkfs time.

> Is there a way to find out my 
> current inode size? "mkfs.xfs -N" does not print its default values on a 
> mounted filesystem and I'm pretty sure I've used the default values when I 
> created the filesystem a while ago (i.e. just plain "mkfs.xfs" w/o any 
> options)

xfs_info <mntpt>

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs