linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Al Boldi" <a1426z@gawab.com>
To: "'Jens Axboe'" <axboe@suse.de>, "'David Masover'" <ninja@slaphack.com>
Cc: "'Chris Wedgwood'" <cw@f00f.org>,
	"'Nathan Scott'" <nathans@sgi.com>, <linux-xfs@oss.sgi.com>,
	<linux-kernel@vger.kernel.org>, <linux-fsdevel@vger.kernel.org>,
	<reiserfs-list@namesys.com>
Subject: RE: XFS corruption during power-blackout
Date: Fri, 1 Jul 2005 17:05:11 +0300	[thread overview]
Message-ID: <200507011405.RAA27425@raad.intranet> (raw)
In-Reply-To: <20050701092412.GD2243@suse.de>

Jens Axboe wrote: {
On Fri, Jul 01 2005, David Masover wrote:
> Chris Wedgwood wrote:
> >On Wed, Jun 29, 2005 at 07:53:09AM +0300, Al Boldi wrote:
> >
> >
> >>What I found were 4 things in the dest dir:
> >>1. Missing Dirs,Files. That's OK.
> >>2. Files of size 0. That's acceptable.
> >>3. Corrupted Files. That's unacceptable.
> >>4. Corrupted Files with original fingerprint. That's ABSOLUTELY 
> >>unacceptable.
> >
> >
> >disk usually default to caching these days and can lose data as a 
> >result, disable that
> 
> Not always possible.  Some disks lie and leave caching on anyway.

And the same (and others) disks will not honor a flush anyways. 
Moral of that story - avoid bad hardware.
}

1. Sync is not the issue. The issue is whether a journaled FS can detect
corrupted files and flag them after a power-blackout!
2. Moral of the story is: What's ext3 doing the others aren't?


  parent reply	other threads:[~2005-07-01 14:07 UTC|newest]

Thread overview: 36+ 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 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
     [not found]         ` <20050701131950.GA15180@ime.usp.br>
2005-07-01 13:57           ` Ric Wheeler
2005-07-01 18:37             ` Bryan Henderson
2005-07-01 18:41               ` Jens Axboe
2005-07-11 12:53                 ` Ric Wheeler
2005-07-01 14:05         ` Al Boldi [this message]
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 18:10               ` Sonny Rao
2005-07-05 19:24                 ` Dieter Nützel
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=200507011405.RAA27425@raad.intranet \
    --to=a1426z@gawab.com \
    --cc=axboe@suse.de \
    --cc=cw@f00f.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=nathans@sgi.com \
    --cc=ninja@slaphack.com \
    --cc=reiserfs-list@namesys.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;
as well as URLs for NNTP newsgroup(s).