linux-kernel - Re: 2.6.39-rc3, 2.6.39-rc4: XFS lockup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sat, 21 May 2011 10:14:31 +1000
From:	Dave Chinner <david@...morbit.com>
To:	Andrey Rahmatullin <wrar@...linux.org>
Cc:	Markus Trippelsdorf <markus@...ppelsdorf.de>,
	Bruno Prémont <bonbons@...ux-vserver.org>,
	xfs-masters@....sgi.com, xfs@....sgi.com,
	Christoph Hellwig <hch@...radead.org>,
	Alex Elder <aelder@....com>,
	Dave Chinner <dchinner@...hat.com>,
	linux-kernel@...r.kernel.org
Subject: Re: 2.6.39-rc3, 2.6.39-rc4: XFS lockup - regression since 2.6.38

On Fri, May 20, 2011 at 05:20:18PM +0600, Andrey Rahmatullin wrote:
> On Fri, Apr 29, 2011 at 11:19:29AM +1000, Dave Chinner wrote:
> > > x4 ~ # xfs_info /
> > > meta-data=/dev/root              isize=256    agcount=4, agsize=1949824 blks
> > >          =                       sectsz=512   attr=2
> > > data     =                       bsize=4096   blocks=7799296, imaxpct=25
> > >          =                       sunit=128    swidth=128 blks
> > > naming   =version 2              bsize=4096   ascii-ci=0
> > > log      =internal               bsize=4096   blocks=3808, version=2
> > >          =                       sectsz=512   sunit=8 blks, lazy-count=1
> > > realtime =none                   extsz=4096   blocks=0, rtextents=0
> > OK, so the common elements here appears to be root filesystems
> > with small log sizes, which means they are tail pushing all the
> > time metadata operations are in progress. 
> Does that mean that such filesystems are not optimal in terms of
> performance and/or reliability and should have larger log sizes?

Performance. Larger logs generally result in faster metadata
performance, but it's really dependent on your workload and storage
as to whether it makes any difference.

Cheers,

Dave.
-- 
Dave Chinner
david@...morbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/