[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.00.0909020743550.22337@p34.internal.lan>
Date: Wed, 2 Sep 2009 07:45:36 -0400 (EDT)
From: Justin Piszcz <jpiszcz@...idpixels.com>
To: Christoph Hellwig <hch@...radead.org>
cc: Nikanth Karthikesan <knikanth@...e.de>,
Jens Axboe <jens.axboe@...cle.com>,
linux-kernel@...r.kernel.org, xfs@....sgi.com
Subject: Re: Kernel 2.6.30.4 loop(..?) regression (& with/2.6.31-rc6)
On Fri, 28 Aug 2009, Justin Piszcz wrote:
>
> On Wed, 26 Aug 2009, Justin Piszcz wrote:
>
>> On Wed, 26 Aug 2009, Christoph Hellwig wrote:
>>
>>> On Wed, Aug 26, 2009 at 05:19:11PM -0400, Justin Piszcz wrote:
Christoph,
Now 6 days without any problems using -o nobarrier.
$ uptime
07:43:55 up 6 days, 14:12, 1 user, load average: 0.00, 0.00, 0.00
So -o nobarrier is a workaround for the issue. How / what debug settings
should be enabled to catch the bug/problem when -o nobarrier is used?
Justin.
--
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/
Powered by blists - more mailing lists