All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@suse.de>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: "Ric Wheeler" <ric@emc.com>,
	linux-fsdevel@vger.kernel.org,
	"Rogério Brito" <rbrito@ime.usp.br>, "Brett Russ" <russb@emc.com>
Subject: Re: XFS corruption during power-blackout
Date: Fri, 1 Jul 2005 20:41:45 +0200	[thread overview]
Message-ID: <20050701184145.GA3055@suse.de> (raw)
In-Reply-To: <OFC37AE538.1F62D48F-ON88257031.00651356-88257031.006642E7@us.ibm.com>

On Fri, Jul 01 2005, Bryan Henderson wrote:
> >>But how does the end-user know what hardware is "good hardware"? Which
> >>vendors don't lie (or, at least, lie less than others) regarding HDs?
> >>
> >
> >The only real way is to test the drive (and retest when you get a new 
> >versions of firmware) and the whole fsync -> write barrier code path.
> 
> Wouldn't a commercial class drive that ignores explicit flushes be 
> infamous?  I'm ready to accept that there are SCSI drives that cache 
> writes in volatile storage by default (but frankly, I'm still skeptical), 
> but I'm not ready to accept that there are drives out there secretly 
> ignoring explicit commands to harden data, thus jeopardizing millions of 
> dollars' worth of data.  I'd need more evidence.

I'm pretty sure I have an IBM drive that does so (its flush cache
command is _really_ fast), as a matter of fact :-) I need to locate it
and put it in a test box to re-ensure this.

I'm not sure such drives would necessarily be infamous, hardly anyone
would notice anything wrong in a desktop type machine. Which is what
these drives were made for.

-- 
Jens Axboe


  reply	other threads:[~2005-07-01 18:40 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20050629001847.GB850@frodo>
2005-06-29  4:53 ` XFS corruption during power-blackout Al Boldi
2005-06-29  4:53   ` Al Boldi
2005-06-29 16:38   ` Christian Rice
2005-06-29 17:02   ` Chris Wedgwood
2005-06-29 17:56     ` Steve Lord
2005-06-29 20:56       ` Chris Wedgwood
2005-06-30 16:30         ` Bryan Henderson
2005-06-30 18:46           ` Chris Wedgwood
2005-06-30 19:44             ` Jörn Engel
2005-06-30 20:32               ` Chris Wedgwood
2005-06-30 21:07                 ` Jörn Engel
2005-07-01 12:36                 ` Ric Wheeler
2005-07-01 12:56                   ` Jens Axboe
2005-06-30 20:49             ` Bryan Henderson
2005-07-01 12:53               ` Ric Wheeler
2005-07-01 18:24                 ` Bryan Henderson
2005-07-01 19:58                   ` David Masover
2005-07-01 21:10                     ` Jörn Engel
2005-07-01 21:39                       ` David Masover
2005-07-01  1:09             ` Stewart Smith
2005-07-05 15:53             ` Sonny Rao
2005-06-29 21:10       ` Nathan Scott
2005-07-01  8:17     ` David Masover
2005-07-01  9:24       ` Jens Axboe
2005-07-01 13:19         ` Rogério Brito
2005-07-01 13:57           ` Ric Wheeler
2005-07-01 13:57             ` Ric Wheeler
2005-07-01 18:37             ` Bryan Henderson
2005-07-01 18:41               ` Jens Axboe [this message]
2005-07-11 12:53                 ` Ric Wheeler
2005-07-01 14:51           ` Luigi Genoni
2005-07-01 14:56             ` Jens Axboe
2005-07-01 14:05         ` Al Boldi
2005-07-01 14:05           ` Al Boldi
2005-07-01 16:35           ` Alistair John Strachan
2005-07-05 15:49           ` Sonny Rao
2005-07-05 17:25             ` Al Boldi
2005-07-05 17:25               ` Al Boldi
2005-07-05 18:10               ` Sonny Rao
2005-07-05 19:24                 ` Dieter Nützel
2005-07-06  4:24                 ` Al Boldi
2005-07-06  4:24                   ` Al Boldi
2005-07-06  4:46                   ` Nathan Scott
2005-07-16  7:02 Al Boldi

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=20050701184145.GA3055@suse.de \
    --to=axboe@suse.de \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=rbrito@ime.usp.br \
    --cc=ric@emc.com \
    --cc=russb@emc.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.