public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Monnerie <michael.monnerie@is.it-management.at>
To: xfs@oss.sgi.com
Subject: Re: xfs data loss
Date: Sun, 6 Sep 2009 11:30:41 +0200	[thread overview]
Message-ID: <200909061130.41912@zmi.at> (raw)
In-Reply-To: <B9A7B002C7FAFC469D4229539E909760308D8CAB6D@DU-EXC-MAIL.empa.emp-eaw.ch>

On Sonntag 06 September 2009 Passerone, Daniele wrote:
> Well, a binary file with 5% data loss would simply not work.
> But I have executables on this filesystem, and they run!

Optimist. It just means the part of the binary you run are not random. 
Randomness of *all* code paths would have to be checked, which you 
probably can't do manually, so binaries are not a good check at all.

Since you didn't change any drives, chances are good that you really 
lost very little data.

> a MB-sized tar.gz file, compression of a postscript file,
> uncompressed perfectly and was visualized in a perfect way by
> ghostview.

That's a good test, so you are lucky.

> Moreover, a device died (a different one) yesterday, and in the
> messages I have ...

Is this on the same controller as the other broken disks were? Then this 
should be it (or it's cabling, or the backplane, etc.). And you should 
immediately shut down the RAID on that controller, as you might loose 
data (or the whole RAID) when the controller writes random data. A 
broken hardware is the worst thing to have. Replace it, test the new 
parts *thouroughly*, and only then start to use the RAID again.

mfg zmi
-- 
// Michael Monnerie, Ing.BSc    -----      http://it-management.at
// Tel: 0660 / 415 65 31                      .network.your.ideas.
// PGP Key:         "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38  500E CE14 91F7 1C12 09B4
// Keyserver: wwwkeys.eu.pgp.net                  Key-ID: 1C1209B4

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

  reply	other threads:[~2009-09-06  9:31 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-06  9:00 xfs data loss Passerone, Daniele
2009-09-06  9:30 ` Michael Monnerie [this message]
2009-09-06 10:43 ` R: " Passerone, Daniele
2009-09-06 21:00 ` Peter Grandi
  -- strict thread matches above, loose matches on Subject: below --
2009-09-04 11:45 Passerone, Daniele
2009-09-03 15:31 Passerone, Daniele
2009-09-05 18:29 ` Peter Grandi
     [not found]   ` <4AA3261E.1000005@sandeen.net>
2009-09-06 20:30     ` Peter Grandi
2009-08-27  7:22 Passerone, Daniele
2009-08-27  9:41 ` Christian Kujau
2009-08-27  9:47   ` Passerone, Daniele
2009-08-27 10:09     ` Christian Kujau
2009-08-27  9:54   ` Passerone, Daniele
2009-08-28  4:16 ` Eric Sandeen
2009-08-28  9:19   ` Passerone, Daniele
2009-08-28 17:17     ` Eric Sandeen
2009-08-28 19:42       ` Passerone, Daniele
2009-08-29  6:08       ` Passerone, Daniele
2009-08-29  7:45         ` Ralf Gross
2009-08-29  7:11       ` Passerone, Daniele
2009-08-29 20:03       ` Passerone, Daniele
2009-08-29 22:14         ` Michael Monnerie
2009-08-29 22:52       ` Passerone, Daniele
2009-08-30  1:24         ` Eric Sandeen
2009-08-30  8:17           ` Michael Monnerie
2009-09-01 12:45         ` Peter Grandi
2009-09-01 22:16           ` Michael Monnerie
2009-09-04 11:08           ` Andi Kleen
2009-08-29 14:08 ` Peter Grandi

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=200909061130.41912@zmi.at \
    --to=michael.monnerie@is.it-management.at \
    --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