linux-lvm.redhat.com archive mirror
 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] Questions regarding LVM
Date: Thu, 3 Dec 2009 13:50:52 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0912031342400.13455@bmsred.bmsi.com> (raw)
In-Reply-To: <89A593F9810AA744B420746E2755B8480DFE0A@xmb-sjc-224.amer.cisco.com>

On Thu, 3 Dec 2009, Vishal Verma -X (vishaver - Embedded Resource Group at Cisco) wrote:

> 1.       Under scenario where, several hard-drives are part of LVM
> volume group and if one of hard-disk gets corrupted then would whole
> volume group be inaccessible ?

Short answer: it depends

Long answer: For raw plain hard drives, only logical volumes using the
affected drive are inaccessible.  Think of LVM as managing fancy run-time
expandable partitions.  You may wish to ensure that the LVM metadata (the LVM
equivalent of the partition table) is stored in multiple locations, or
frequently backed up from /etc/lvm.

More often, the "drives" that are part of LVM are software or hardware RAID
drives.  In addition, Linux LVM supports mirroring (RAID1) at the LV level
- although not yet as smoothly as other LVM systems.

> What would be impact on volume group's filesystem ?

Same as with any other partition that goes south.

> 2.       From stability perspective, which version of LVM is better on
> Linux kernel 2.6.x, LVM2 or LVM1 ?

LVM2

-- 
	      Stuart D. Gathman <stuart@bmsi.com>
    Business Management Systems Inc.  Phone: 703 591-0911 Fax: 703 591-6154
"Confutatis maledictis, flammis acribus addictis" - background song for
a Microsoft sponsored "Where do you want to go from here?" commercial.

      parent reply	other threads:[~2009-12-03 18:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-03 18:22 [linux-lvm] Questions regarding LVM Vishal Verma -X (vishaver - Embedded Resource Group at Cisco)
2009-12-03 18:42 ` malahal
2009-12-03 18:43 ` Ray Morris
2009-12-03 18:50 ` Stuart D. Gathman [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=Pine.LNX.4.64.0912031342400.13455@bmsred.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 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).