All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stuart D Gathman <stuart@bmsi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] HDD failure - please help!
Date: Thu, 02 Sep 2010 11:22:19 -0400	[thread overview]
Message-ID: <4C7FC12B.40009@bmsi.com> (raw)
In-Reply-To: <2E9263050F8EE046972BE0510E7A71DA03D99F3C@SH-EXCHBE2.master.lsuhsc.edu>

On 09/02/2010 07:50 AM, Patterson, James wrote:
>> If you wanted RAID5, your best bet on linux is the md driver.
>> Or else a hardware RAID controller.
>>      
> I don't/didn't want RAID.
>    

Based on your expectations, I think you *do* want at least RAID1.  Raid 
1 is simple to administer
and understand.
>> your first step is getting a copy of the metadata.
>> There should be a copy at the beginning of each drive.
>>      
> Yes. How do I access it? None of the drives will mount. I am thinking here that I should create a special boot disk with the LVM tools on it (they are not present on the FC11 boot iso, afaik).
>    
You don't mount the PVs.   Use the metadata extraction tool, I don't 
remember the name atm.
If this was your boot filesystem, then you will need a LiveCD or new 
install.  Since you will need a new disk anyway, I suggest you get the 
new disk that is *bigger* than the failing drive and install to it (but 
*not* overwriting the others) and leave a partition big enough to 
contain the PV from the failing drive.  Remove the failing drive, and 
access it via USB - even if you have another drive slot.  By taking 
steps to keep it as cold as possible during recovery, you can coax a few 
more sectors out of it.
>> then you should look back a month or so in the archives
>>      
> I looked...could you please be a bit more specific? I didn't see anything.
>    
This should get you started:  
https://www.redhat.com/archives/linux-lvm/2010-July/msg00057.html
> Well, truly, the only thing I've learned is never to use LVM if it's 
> going to cause me to lose data on all 5 drives when one goes down. The 
> logic behind it's use appears to be to just make life "easier"
With jbod (which you likely have), the failure scenario is exactly the 
same whether you have 1 disk or 5.  Part of your filesystem gets 
trashed, and you have to use low level tools to recover what remains if 
you don't have backups.

What having 5 disks *does* do is make failure more likely.  Suppose the 
probability of 1 disk *not* failing in a given year is .999 (3 sigmas).  
With jbod, the LV fails if *any* of the disks fail.  The probability 
that none of them fail in a given year would then be .999^5 ~= .995.  
Your array is less reliable.

By using RAID, you can make the array more reliable.  RAID works by 
using multiple copies of data so that you don't lose anything on a 
single drive failure.

  reply	other threads:[~2010-09-02 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.25972.1283360318.9817.linux-lvm@redhat.com>
2010-09-02 11:50 ` [linux-lvm] HDD failure - please help! Patterson, James
2010-09-02 15:22   ` Stuart D Gathman [this message]
2010-09-01 16:57 Patterson, James
2010-09-01 17:14 ` Stuart D. Gathman

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=4C7FC12B.40009@bmsi.com \
    --to=stuart@bmsi.com \
    --cc=linux-lvm@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.