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, 30 Aug 2009 00:14:13 +0200	[thread overview]
Message-ID: <200908300014.13845@zmi.at> (raw)
In-Reply-To: <B9A7B002C7FAFC469D4229539E909760308DA65407@DU-EXC-MAIL.empa.emp-eaw.ch>

On Samstag 29 August 2009 Passerone, Daniele wrote:
> 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.

Right, if you communicated this to users it's OK.

But really, don't create any RAID with more than 8 data disks. 
Performance doesn't increase above that, and the chance that a single 
disk dies is already 8x as high as with a single disk.

I wish you luck with your recovery, but please try to split your 20 
disks, make it 2x9 disks with a RAID-5, better RAID-6, and connect those 
two via RAID-0. So you get a RAID-50 or RAID-60. Take the remaining 2 
drives as hot spare. This will protect you at least from drive failures, 
and speeds up recreating the RAID when a disk dies.
Try to connect the disks which are in a single RAID-5/6 via the same 
controllers, so if a controller dies it's only one RAID-5/6 part that 
dies, which will help to make it possible to repair.

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-08-29 22:13 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 [this message]
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
  -- 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=200908300014.13845@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