xfs
[Top] [All Lists]

Re: Kernel 2.6.30.4 XFS(..?) regression (happened again)

To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Subject: Re: Kernel 2.6.30.4 XFS(..?) regression (happened again)
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Sat, 15 Aug 2009 22:23:31 -0400
Cc: Felix Blyakher <felixb@xxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.0908110624420.22426@xxxxxxxxxxxxxxxx>
References: <alpine.DEB.2.00.0908080422440.12329@xxxxxxxxxxxxxxxx> <00980BBF-1206-4BEF-A8AE-B4A8DAE7EC27@xxxxxxx> <alpine.DEB.2.00.0908090605080.16485@xxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0908110624420.22426@xxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.19 (2009-01-05)
All your traces seem to have in common that you're block on locks hold
by processed doing I/O.  Especially a lot of page locks which are
controlled by the VM and not the filesystem.  Can you try with commit
8aa7e847d834ed937a9ad37a0f2ad5b8584c1ab0 from 2.6.31-rc applied, or
better directly 2.6.3-rc6?

I would be surprised if this is something inside XFS, but running with
CONFIG_XFS_DEBUG never hurts.

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