Re: Which kernel options should be enabled to find the root cause of this bug?

All of lore.kernel.org
 help / color / mirror / Atom feed

From: Eric Sandeen <sandeen@sandeen.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org, Alan Piszcz <ap@solarrain.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Which kernel options should be enabled to find the root cause of this bug?
Date: Tue, 24 Nov 2009 10:23:26 -0600	[thread overview]
Message-ID: <4B0C087E.6050701@sandeen.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0911241115080.7755@p34.internal.lan>

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

WARNING: multiple messages have this Message-ID (diff)

From: Eric Sandeen <sandeen@sandeen.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org, Alan Piszcz <ap@solarrain.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Which kernel options should be enabled to find the root cause of this bug?
Date: Tue, 24 Nov 2009 10:23:26 -0600	[thread overview]
Message-ID: <4B0C087E.6050701@sandeen.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0911241115080.7755@p34.internal.lan>

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

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

next prev parent reply	other threads:[~2009-11-24 16:23 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-17 22:34 2.6.31+2.6.31.4: XFS - All I/O locks up to D-state after 24-48 hours (sysrq-t+w available) Justin Piszcz
2009-10-17 22:34 ` Justin Piszcz
2009-10-18 20:17 ` Justin Piszcz
2009-10-18 20:17   ` Justin Piszcz
2009-10-19  3:04   ` Dave Chinner
2009-10-19  3:04     ` Dave Chinner
2009-10-19 10:18     ` Justin Piszcz
2009-10-19 10:18       ` Justin Piszcz
2009-10-20  0:33       ` Dave Chinner
2009-10-20  0:33         ` Dave Chinner
2009-10-20  8:33         ` Justin Piszcz
2009-10-20  8:33           ` Justin Piszcz
2009-10-21 10:19           ` Justin Piszcz
2009-10-21 10:19             ` Justin Piszcz
2009-10-21 14:17             ` mdadm --detail showing annoying device Stephane Bunel
2009-10-21 21:46               ` Neil Brown
2009-10-22 11:22                 ` Stephane Bunel
2009-10-29  3:44                   ` Neil Brown
2009-11-03  9:37                     ` Stephane Bunel
2009-11-03 10:09                       ` Beolach
2009-11-03 12:16                         ` Stephane Bunel
2009-10-22 11:29                 ` Mario 'BitKoenig' Holbe
2009-10-22 14:17                   ` Stephane Bunel
2009-10-22 16:00                     ` Stephane Bunel
2009-10-22 22:49             ` 2.6.31+2.6.31.4: XFS - All I/O locks up to D-state after 24-48 hours (sysrq-t+w available) Justin Piszcz
2009-10-22 22:49               ` Justin Piszcz
2009-10-22 23:00               ` Dave Chinner
2009-10-22 23:00                 ` Dave Chinner
2009-10-26 11:24               ` Justin Piszcz
2009-10-26 11:24                 ` Justin Piszcz
2009-11-02 21:46                 ` Justin Piszcz
2009-11-02 21:46                   ` Justin Piszcz
2009-11-20 20:39             ` 2.6.31+2.6.31.4: XFS - All I/O locks up to D-state after 24-48 hours (sysrq-t+w available) - root cause found = asterisk Justin Piszcz
2009-11-20 20:39               ` Justin Piszcz
2009-11-20 23:44               ` Bug#557262: " Faidon Liambotis
2009-11-20 23:44                 ` Faidon Liambotis
2009-11-20 23:44                 ` Faidon Liambotis
2009-11-20 23:51                 ` Justin Piszcz
2009-11-20 23:51                   ` Justin Piszcz
2009-11-21 14:29                 ` Roger Heflin
2009-11-21 14:29                   ` Roger Heflin
2009-11-24 13:08 ` Which kernel options should be enabled to find the root cause of this bug? Justin Piszcz
2009-11-24 13:08   ` Justin Piszcz
2009-11-24 15:14   ` Eric Sandeen
2009-11-24 15:14     ` Eric Sandeen
2009-11-24 16:20     ` Justin Piszcz
2009-11-24 16:20       ` Justin Piszcz
2009-11-24 16:23       ` Eric Sandeen [this message]
2009-11-24 16:23         ` Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4B0C087E.6050701@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=ap@solarrain.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Be sure your reply has a Subject: header at the top and a blank line before the message body.

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.