Linux LVM users
 help / color / mirror / Atom feed
From: lembark@wrkhors.com
To: linux-lvm@sistina.com, Quentin Arce <qarce@yahoo.com>
Subject: Re: [linux-lvm] Does LVM detect drive failures?
Date: Tue Nov  6 11:43:02 2001	[thread overview]
Message-ID: <320450000.1005068617@duke.wrkhors.com> (raw)
In-Reply-To: <20011106172021.75477.qmail@web20003.mail.yahoo.com>


-- Quentin Arce <qarce@yahoo.com> on 11/06/01 09:20:21 -0800

> Hello,
> 
>  I'm not on the mailing list so please reply to all. 
> Thanks.
> My question is does LVM detect drive failures?  I am
> thinking about building two small logical volumes of 2
> drives each then mirroring them using md.  I know md
> will detect that the array contains a failed drive
> under normal conditions, but I would think that in
> this case an entire logical volume would have to fail
> in order for it to be detected.  That is unless I can
> watch my logs for LVM giving me an error like I do for
> md errors.
> 
>  One other question... I'll search the md info if no
> one knows this off the top...  does the md layer store
> info about the size of the drive on the drive?  I'm
> worried about adding more dives to a logical volume
> which is a part of a md stripe.

LVM is going to have more problems with hardware failures
than RAID. You are better off building VG's out of mirrored
PV's (or, if you have 2+ drives w/tih 4+ partitions use
RAID5). The RAID will keep PV's available for LVM.

--
Steven Lembark                              2930 W. Palmer
Workhorse Computing                      Chicago, IL 60647
                                           +1 800 762 1582

      reply	other threads:[~2001-11-06 11:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-06 11:19 [linux-lvm] Does LVM detect drive failures? Quentin Arce
2001-11-06 11:43 ` 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=320450000.1005068617@duke.wrkhors.com \
    --to=lembark@wrkhors.com \
    --cc=linux-lvm@sistina.com \
    --cc=qarce@yahoo.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