From: pg_xf2@xf2.for.sabi.co.UK (Peter Grandi)
To: Linux XFS <xfs@oss.sgi.com>
Subject: Re: xfs data loss
Date: Sun, 6 Sep 2009 21:00:07 +0000 [thread overview]
Message-ID: <19108.8919.46775.810693@tree.ty.sabi.co.uk> (raw)
In-Reply-To: <B9A7B002C7FAFC469D4229539E909760308D8CAB6D@DU-EXC-MAIL.empa.emp-eaw.ch>
[ ... ]
>> The original 20 devices or did you put in 2 new blank hard
>> drives? I feel like that 2 blank drives went in, but then
>> later I read that all [original] 20 drives could be read for
>> a few MB at the beginning.
> No. No blank drives went in. And I always used the original 20
> devices.
That may be very good news (or not if some are partially
damaged).
[ ... ]
> I therefore suspect that the "broken devices" indication,
> since it is repeatedly found in the last weeks, and always for
> different devices/filesystems, has to do with the RAID
> controller, and not with a specific device failure-.
But a broken RAID host adapter can write random stuff to
some/most disks and can continue to do so. Unless the RAID host
adapter had a temporary failure. But who knows?
>> * Somehow 'xfs_repair' managed to rebuild the metadata of
>> '/dev/md5' despite a loss of 5-6% of it, so it looks
>> "consistent" as far as XFS is concerned, but up to 5-6% of
>> each file is essentially random, and it is very difficult to
>> know where the random part are.
> I don't see any element to support this - at present.
Well, the only thing is known for sure at this point is that an
event happened that physically damaged some parts of the system,
this damage includes some drives out of the 48 that died, and
there was huge data loss *apparently* without cause, as in the
arrays where data loss happened all drives are at least
partially working, but some have been failing afterwards,
and anyhow the arrays would not resync afterwards.
Given this background, I would not assume *anything* really
works unless it is proven to work with fairly challenging
testing.
Thus the repeated advice to do a thorough read check of all
drives. I would also check the error log of all drives with
'smartctl -l error' but if there was an electric shock the drive
might not have been able to log anything.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-09-09 13:47 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
2009-09-06 10:43 ` R: " Passerone, Daniele
2009-09-06 21:00 ` Peter Grandi [this message]
-- 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=19108.8919.46775.810693@tree.ty.sabi.co.uk \
--to=pg_xf2@xf2.for.sabi.co.uk \
--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