All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>,
	linux-kernel@vger.kernel.org, xfs@oss.sgi.com,
	Alan Piszcz <ap@solarrain.com>
Subject: Re: Intel X25-E running Linux using XFS
Date: Mon, 22 Dec 2008 03:50:47 -0500	[thread overview]
Message-ID: <20081222085047.GA24795@infradead.org> (raw)
In-Reply-To: <20081212185803.GE11974@elf.ucw.cz>

On Fri, Dec 12, 2008 at 07:58:03PM +0100, Pavel Machek wrote:
> Actually I'd like to know... how does it behave during powerfails
> while it is being written to?

I've done various powerfail tests with and X25-M and as expect it
behaves perfectly fine as long as you either disable the write cache
or use barriers.  The default ext3 setup without barriers corrupts
the filesystem left, right and center, but that's the same as other
recent disk drives with large caches.


WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Pavel Machek <pavel@suse.cz>
Cc: Alan Piszcz <ap@solarrain.com>,
	xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: Intel X25-E running Linux using XFS
Date: Mon, 22 Dec 2008 03:50:47 -0500	[thread overview]
Message-ID: <20081222085047.GA24795@infradead.org> (raw)
In-Reply-To: <20081212185803.GE11974@elf.ucw.cz>

On Fri, Dec 12, 2008 at 07:58:03PM +0100, Pavel Machek wrote:
> Actually I'd like to know... how does it behave during powerfails
> while it is being written to?

I've done various powerfail tests with and X25-M and as expect it
behaves perfectly fine as long as you either disable the write cache
or use barriers.  The default ext3 setup without barriers corrupts
the filesystem left, right and center, but that's the same as other
recent disk drives with large caches.

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

  parent reply	other threads:[~2008-12-22  8:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-27 21:54 Intel X25-E running Linux using XFS Justin Piszcz
2008-11-27 21:54 ` Justin Piszcz
2008-11-27 21:54 ` Justin Piszcz
2008-11-27 22:12 ` Russell Smith
2008-12-12 18:58 ` Pavel Machek
2008-12-12 18:58   ` Pavel Machek
2008-12-12 20:23   ` Justin Piszcz
2008-12-12 20:23     ` Justin Piszcz
2008-12-13 11:43     ` Stefan Richter
2008-12-13 11:43       ` Stefan Richter
2008-12-20 19:47     ` Volker Kuhlmann
2008-12-12 23:06   ` Volker Kuhlmann
2008-12-22  8:50   ` Christoph Hellwig [this message]
2008-12-22  8:50     ` Christoph Hellwig

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=20081222085047.GA24795@infradead.org \
    --to=hch@infradead.org \
    --cc=ap@solarrain.com \
    --cc=jpiszcz@lucidpixels.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --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.