linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Brown <david.brown@hesbynett.no>
To: linux-raid@vger.kernel.org
Subject: Re: Direct disk access on IBM Server
Date: Sat, 23 Apr 2011 16:42:27 +0200	[thread overview]
Message-ID: <iouogj$h43$1@dough.gmane.org> (raw)
In-Reply-To: <BANLkTi=CLD=Cd0Ngj1hXqQtz3Cb6ir4yRg@mail.gmail.com>

On 23/04/11 16:05, Majed B. wrote:
> Hello,
>
> I've setup a bunch of software RAID boxes and I've had my main one
> running at a friend's place with about 16 disks and 9TB of data.
>
> One time 2 disks had bad sectors and things took a bad turn. It was a
> RAID5 array, so I had to salvage everything I could rather than losing
> everything we had there (no backups). It took me about 3 weeks of
> working daily for about 6 hours a day in cloning disks, recovering
> files and validating checksums. It was not fun at all.
>

There's good reason for recommending raid6 for such large arrays!

I really hope Neil (or someone else) gets the chance to implement the 
features in the md roadmap - once md supports bad block lists, bad 
blocks on a disk will no longer mean the whole disk is removed.  So in 
situations like yours, unless you have bad sectors at the same place on 
two drives, all your data will be intact - and the huge majority will 
still be redundant, giving you time to do a simple disk replacement.

> If you have critical data, I'd suggest you add a battery and an
> sd-card/flash card to your hardware RAID array. At least if the power
> goes off, whatever is in the cache will be written to the card and
> later on to the disks when power is restored.
>
> A UPS will not help you if your power supply decides to commit seppuku.
>

That's true, of course.  But protecting data is always a matter of 
minimising the risks and consequences of the more likely failures.  My 
power supply /could/ fail, but I don't see it as a likely case.  With a 
good UPS and some redundancy in the disks, by far the most likely cause 
of failure is human error (someone deleting the wrong file, for 
instance).  Still, I will be checking the price of a backup battery for 
the server.

> If you keep daily backups, or any form of backups, go ahead with
> software RAID and keep yourself free from vendor lock.
>

I do have daily backups - raid doesn't prevent /all/ data loss!

mvh.,

David


> Regards,
>
> On Thu, Apr 21, 2011 at 2:36 PM, David Brown<david.brown@hesbynett.no>  wrote:
>> On 21/04/11 08:24, Stan Hoeppner wrote:
>>>
>>> David Brown put forth on 4/20/2011 7:21 AM:
>>>
>>>> It's true that boot loaders and software raid can be an awkward
>>>> combination.
>>>
>>> ...
>>>>
>>>> Yes, it's a few extra steps.



  reply	other threads:[~2011-04-23 14:42 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 13:21 Direct disk access on IBM Server David Brown
2011-04-19 13:25 ` Mathias Burén
2011-04-19 14:04   ` David Brown
2011-04-19 14:07     ` Mathias Burén
2011-04-19 15:12       ` David Brown
2011-04-19 15:41         ` Mathias Burén
2011-04-20  8:08           ` David Brown
2011-04-19 20:08 ` Stan Hoeppner
2011-04-20 11:24   ` David Brown
2011-04-20 11:40     ` Rudy Zijlstra
2011-04-20 12:21       ` David Brown
2011-04-21  6:24         ` Stan Hoeppner
2011-04-21 11:36           ` David Brown
2011-04-23 14:05             ` Majed B.
2011-04-23 14:42               ` David Brown [this message]
2011-04-24 12:48             ` Drew
2011-04-24 20:00               ` David Brown
2011-04-24 20:25                 ` Rudy Zijlstra
2011-04-25  9:42                   ` David Brown
2011-04-21  3:50     ` Ryan Wagoner
2011-04-21 11:00       ` David Brown
2011-04-21  4:10     ` Stan Hoeppner
2011-04-21 11:19       ` David Brown

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='iouogj$h43$1@dough.gmane.org' \
    --to=david.brown@hesbynett.no \
    --cc=linux-raid@vger.kernel.org \
    /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).