All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Lembark <lembark@wrkhors.com>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] What happens when a disk dies?
Date: Fri, 11 May 2001 14:41:10 -0500	[thread overview]
Message-ID: <3AFC4056.D013D2B6@wrkhors.com> (raw)
In-Reply-To: 85256A49.0053DE83.00@janus.eci.esys.com

> I am very interested in starting to use LVM.  We have large amounts of data
> that is fairly dynamic.  Since it is dynamic, we don't need to incur the
> cost expensive SCSI RAID solutions for data integrity.  We currently use
> four 80 Gig Maxtor Hard Drives to store our data at test events. Of course
> this means with a /drive1 /drive2 /drive3 and a /drive4 directory.  So the
> user has to search the drives to find the file of interest.  We kind of
> hide this by creating links but the links need to be periodically updated
> as files are added or deleted.  LVM solves this problem.  But before I move
> to LVM, I curious on what happens if a drive dies.
> 
>  If drive2 goes down and I replace it with another drive, do I just lose
> the data on drive2 or do I lose all of the data in the Logical Volume?
> 
> If I don't lose the data on the other drives, can LVM also be reconfigured
> to remove the dead drive and then continue working with just the other
> three drives (only losing the data on the dead drive)?
> 
> I read the FAQs and one of them shows how to recover from a dead drive.  It
> is says you lose the data in the Logical Volume but I'm hoping just the
> data on the physical disk that died and not the entire volume.


LVM will not replace mirroring or RAID solutions.  for lots of
dynamic data the best solution will probably be hardware RAID
for the physical layer with LVM using RAID volumes as PV's.

e.g., if you can 4 disks into a RAID5 set then take the whole
RAID volume and use the entire space as a single PV.  you can
then group multiple PV's together into a single VG.  this VG
then gets divied up for the users into various LV's which get
mounted wherever the folks are supposed to use them.  you can
expand an LV within the VG (example:  you just bought 4 more
disks and need to expand existing space into them).  

nice thing about this arrangement is that you can have huge amounts
of total space without needing to expose all of it at once or
drop and rebiuld the filesystems to grow them.  when someone
really does run out of space (or someone new needs it) just expand
or create a LV and go along with life.


-- 
 Steven Lembark                                   2930 W. Palmer St.
                                                 Chicago, IL  60647
 lembark@wrkhors.com                                   800-762-1582

      parent reply	other threads:[~2001-05-11 19:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-11 15:16 [linux-lvm] What happens when a disk dies? Kyle_S_Hoyt
2001-05-11 15:30 ` Adrian Phillips
2001-05-11 17:28 ` Heinz J. Mauelshagen
2001-05-11 19:41 ` Steven Lembark [this message]

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=3AFC4056.D013D2B6@wrkhors.com \
    --to=lembark@wrkhors.com \
    --cc=linux-lvm@sistina.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.