xfs
[Top] [All Lists]

Re: Which kernel options should be enabled to find the root cause of thi

To: Justin Piszcz <jpiszcz@xxxxxxxxxxxxxxx>
Subject: Re: Which kernel options should be enabled to find the root cause of this bug?
From: Eric Sandeen <sandeen@xxxxxxxxxxx>
Date: Tue, 24 Nov 2009 10:23:26 -0600
Cc: linux-raid@xxxxxxxxxxxxxxx, Alan Piszcz <ap@xxxxxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.0911241115080.7755@xxxxxxxxxxxxxxxx>
References: <alpine.DEB.2.00.0910171825270.16781@xxxxxxxxxxxxxxxx> <alpine.DEB.2.00.0911240805490.25676@xxxxxxxxxxxxxxxx> <4B0BF866.7040004@xxxxxxxxxxx> <alpine.DEB.2.00.0911241115080.7755@xxxxxxxxxxxxxxxx>
User-agent: Thunderbird 2.0.0.21 (X11/20090320)
Justin Piszcz wrote:
> 
> On Tue, 24 Nov 2009, Eric Sandeen wrote:

...

>> Do you get the same behavior if you don't add the log options at mount time?
> I have not tried disabling the log options, although they have been in effect
> for a long time, (the logsbufs and bufsize and recently) the nobarrier
> support.  Could there be an issue using -o nobarrier on a raid1+xfs?

nobarrier should not cause problems.

-Eric

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