xfs
[Top] [All Lists]

Re: Kernel 2.6.30.4 loop(..?) regression (& with/2.6.31-rc6)

To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Subject: Re: Kernel 2.6.30.4 loop(..?) regression (& with/2.6.31-rc6)
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 26 Aug 2009 14:02:34 -0400
Cc: Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, Nikanth Karthikesan <knikanth@xxxxxxx>, Jens Axboe <jens.axboe@xxxxxxxxxx>
In-reply-to: <alpine.DEB.2.00.0908260949550.9396@xxxxxxxxxxxxxxxx>
References: <alpine.DEB.2.00.0908220624440.30321@xxxxxxxxxxxxxxxx> <20090822142550.GA10003@xxxxxxxxxxxxx> <alpine.DEB.2.00.0908221044420.30321@xxxxxxxxxxxxxxxx> <20090822201558.GA17955@xxxxxxxxxxxxx> <alpine.DEB.2.00.0908221645440.20848@xxxxxxxxxxxxxxxx> <20090822205502.GA18904@xxxxxxxxxxxxx> <alpine.DEB.2.00.0908221659030.23463@xxxxxxxxxxxxxxxx> <20090823224504.GA19942@xxxxxxxxxxxxx> <alpine.DEB.2.00.0908240704130.9427@xxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0908260949550.9396@xxxxxxxxxxxxxxxx>
User-agent: Mutt/1.5.19 (2009-01-05)
On Wed, Aug 26, 2009 at 09:50:27AM -0400, Justin Piszcz wrote:
> So far the uptime is 2 days, if it does not recur in the next 24-48 
> hours, do you recommend I follow up with the linux-crypto folks about 
> this?  It appears this could be the cause (no issues, as of yet).

At this point it doesn't look crypto related anymore, but like some
bad interaction between layers once we add those fsync in the loop code.

What filesystem does you loop image reside on?   Anything else special?
Any way to trgiger it with just loop but not crypto, etc.

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