From: Ray Morris <support@bettercgi.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Questions regarding LVM
Date: Thu, 03 Dec 2009 12:43:56 -0600 [thread overview]
Message-ID: <1259865836.6713.13@raydesk1.bettercgi.com> (raw)
In-Reply-To: <89A593F9810AA744B420746E2755B8480DFE0A@xmb-sjc-224.amer.cisco.com> (from vishaver@cisco.com on Thu Dec 3 12:22:11 2009)
> 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 ?
See the --partial option. See also vgcfgrestore. (rtfm)
Basically, if the drive is merely "corrupted" as you said,
there could be some currupted data. If the drive is missing
or largely unuseable those extents are gone, so LVs with
important extents on that PV would have serious problems,
but LVs with no extents on that PV should be fine. "Important"
extents means, for example, if a 400GB LV which is only 10%
full has only it's last couple on extents on the missing PV
that may not be a major problem, if no data is stored there
yet. On the other hand, the first extent of the filesystem
probably contains very important information about the
filesystem as a whole, so if that first extent is unuseable
you're probably reduced to greping the LV, or using an automated
search tool that basically greps the LV - the same type of
tools used for undelete or corrupted disks without LVM.
> What would be impact on volume group's filesystem ?
VGs don't have filesystems. LVs do. This is the same
question as "if I'm NOT using LVM and parts of my drive go
bad what is the effect on the filesystem?" The ability to
salvage files from the filesystems of affected LVs depends
on how many extents are missing or corrupted, which extents
those are, and what type of filesystem is used.
So in summary, LVM doesn't change much in terms of the
affect of a bad disk. You should still have really solid
backups and probably use RAID.
--
Ray Morris
support@bettercgi.com
Strongbox - The next generation in site security:
http://www.bettercgi.com/strongbox/
Throttlebox - Intelligent Bandwidth Control
http://www.bettercgi.com/throttlebox/
Strongbox / Throttlebox affiliate program:
http://www.bettercgi.com/affiliates/user/register.php
On 12/03/2009 12:22:11 PM, Vishal Verma -X (vishaver - Embedded
Resource Group at Cisco) wrote:
> Hello all,
>
>
>
> I am new to this mailing list. I have few questions regarding
> Linux
> LVM, would appreciate if LVM gurus could answer.
>
>
>
>
>
> 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 ?
>
> What would be impact on volume group's filesystem ?
>
>
>
> 2. From stability perspective, which version of LVM is better on
> Linux kernel 2.6.x, LVM2 or LVM1 ?
>
>
>
> Regards,
>
> Vishal
>
>
>
>
------quoted attachment------
> _______________________________________________
> linux-lvm mailing list
> linux-lvm@redhat.com
> https://www.redhat.com/mailman/listinfo/linux-lvm
> read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
next prev parent reply other threads:[~2009-12-03 18:44 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 [this message]
2009-12-03 18:50 ` 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=1259865836.6713.13@raydesk1.bettercgi.com \
--to=support@bettercgi.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.