From: Eric Sandeen <sandeen@sandeen.net>
To: "Passerone, Daniele" <Daniele.Passerone@empa.ch>
Cc: "xfs@oss.sgi.com" <xfs@oss.sgi.com>
Subject: Re: xfs data loss
Date: Sat, 29 Aug 2009 18:24:47 -0700 [thread overview]
Message-ID: <4A99D4DF.50003@sandeen.net> (raw)
In-Reply-To: <B9A7B002C7FAFC469D4229539E909760308DA65408@DU-EXC-MAIL.empa.emp-eaw.ch>
Passerone, Daniele wrote:
> I would like to ask mr. Peter Grandi, whether it is really necessary
> to delivery ist vaste knowledge in such a harsh way. Is this the
> habit of this mailing list?
Not generally.
> Apart from that, thank you for you help. I understand that RAID5 is
> not the ideal solution for that system, and I admit that in the
> urgence of solving the /md4 problem I miswrote the problem of /md6,
> which of course was "erased" and not "repaired".
>
> But apart from that, it is not as easy to backup 20 TB, so we decided
> to set it as data storage leaving the responsibilty of the backup to
> our users. I do not consider it completely absurd.
I think others have pointed out, though, that you start -increasing- the
risk of failure at a certain point...
> Moreover, when a raid loses 2 devices, and the devices are still ok,
> it is possible to reassemble the raid by assuming the devices clean.
>
> This is not the case for /Raid/md4, where apparently all devices are
> there.
This all seems most likely to be a raid failure problem, but it's hard
to know. I can't imagine why you're getting suddenly-disappearing
directories without a reboot or even a single error message; I just
don't know what to make of that.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-08-30 1:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 7:22 xfs data loss 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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-09-04 11:45 Passerone, Daniele
2009-09-06 9:00 Passerone, Daniele
2009-09-06 9:30 ` Michael Monnerie
2009-09-06 21:00 ` 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=4A99D4DF.50003@sandeen.net \
--to=sandeen@sandeen.net \
--cc=Daniele.Passerone@empa.ch \
--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