public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Christoph Hellwig <hch@infradead.org>,
	Nikanth Karthikesan <knikanth@suse.de>,
	Jens Axboe <jens.axboe@oracle.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: Kernel 2.6.30.4 loop(..?) regression (& with/2.6.31-rc6)
Date: Fri, 28 Aug 2009 12:55:26 -0400	[thread overview]
Message-ID: <20090828165526.GA6133@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0908280720220.30806@p34.internal.lan>

On Fri, Aug 28, 2009 at 07:23:11AM -0400, Justin Piszcz wrote:
> If both '-o nobarrier' and the patch solves the issue, what is the next  
> action that should be taken?  Update the documentation to always use
> -o nobarrier for cryptoloop? Or get the patch reverted in mainline?

We'll have to figure out why it causes those problems and how fix them.
-o nobarrier on a loop device is extremly unsafe as you will possible
lose large amounts of log updates in case of a crash.

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

  reply	other threads:[~2009-08-28 16:57 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-08  8:39 Kernel 2.6.30.4 XFS(..?) regression Justin Piszcz
2009-08-08 19:31 ` Felix Blyakher
2009-08-09 10:09   ` Justin Piszcz
2009-08-11 10:58     ` Kernel 2.6.30.4 XFS(..?) regression (happened again) Justin Piszcz
2009-08-16  2:23       ` Christoph Hellwig
2009-08-17 14:25         ` Justin Piszcz
2009-08-22 10:27           ` Kernel 2.6.30.4 XFS(..?) regression (& with/2.6.31-rc6) Justin Piszcz
2009-08-22 14:25             ` Christoph Hellwig
2009-08-22 14:45               ` Justin Piszcz
2009-08-22 20:15                 ` Christoph Hellwig
2009-08-22 20:46                   ` Justin Piszcz
2009-08-22 20:55                     ` Christoph Hellwig
2009-08-22 21:01                       ` Justin Piszcz
2009-08-23 22:45                         ` Christoph Hellwig
2009-08-24 11:04                           ` Justin Piszcz
2009-08-26 13:50                             ` Justin Piszcz
2009-08-26 18:02                               ` Kernel 2.6.30.4 loop(..?) " Christoph Hellwig
2009-08-26 21:19                                 ` Justin Piszcz
2009-08-26 21:27                                   ` Christoph Hellwig
2009-08-26 21:31                                     ` Justin Piszcz
2009-08-28 11:23                                       ` Justin Piszcz
2009-08-28 16:55                                         ` Christoph Hellwig [this message]
2009-09-02 11:45                                         ` Justin Piszcz

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=20090828165526.GA6133@infradead.org \
    --to=hch@infradead.org \
    --cc=jens.axboe@oracle.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=knikanth@suse.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox