From: Jordi Prats <jprats@cesca.es>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM Questions
Date: Wed, 02 Apr 2008 10:20:02 +0200 [thread overview]
Message-ID: <47F341B2.2080100@cesca.es> (raw)
In-Reply-To: <C35C6F42A97E0C468C32F3AEE46CFF640401D788@digiexch03.iodigi.ioroot.tld>
Hi,
You could still use raid using pvmove: You could create a raid and then
use pvmove to relocate data present on your disk to your new raid device.
cheers,
Jordi
Nicholas Muguira wrote:
>
> I am trying to judge the ability of LVM to address a problem I
> currently have, and I have few questions:
>
> 1) Is there a way to configure LVM so that the data on remaining PV�s
> in a VG are is accessible after a PV fails?
>
> 2) Is there a way to configure LVM so that the LV will still be
> accesible and readable/writable if a PV fails while in use?
>
> 3) Assuming groupings of external drives, can a LV be created and
> exported on each group of the same name and then imported into
> different systems. For example assuming 10 drives, drives a-e are in
> group 1 and drives f-j are in group 2. Using System A with drives a-e
> connect to /dev/sda-e create a parittion that spans the entire drive
> for each drive. Create a PV on each partition (/dev/sd[a-e]1). Create
> a VG named test with all partitions (/dev/sd[a-e]1). Create a LV that
> covers all of the VG test. Mount the LV and format it (ext3 in this
> case). Umount and vgexport the vg test. Repeat the steps with drives
> f-j with same VG and LV names. Connect group 1 to System B and
> vgimport VG test, create LV with it and mount the filesystem. Umount
> the filesystem and disconnect group1. Connect group 2 to System B and
> vgimport VG test and mount the filesystem (using LV previously created)?
>
> Raid is unavailable due to already deployed hardware, and I realize
> that LVM is not Raid and will not give me a means to recover the data
> on the failed HDD.
>
> Thanks,
> Nick
>
> This email and any files transmitted with it are confidential and are
> intended solely for the use of the individual or entity to whom they
> are addressed. If you are not the original recipient or the person
> responsible for delivering the email to the intended recipient, be
> advised that you have received this email in error, and that any use,
> dissemination, forwarding, printing, or copying of this email is
> strictly prohibited. If you received this email in error, please
> immediately notify the sender and delete the original.
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> 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/
--
......................................................................
__
/ / Jordi Prats
C E / S / C A Dept. de Sistemes
/_/ Centre de Supercomputaci� de Catalunya
Gran Capit�, 2-4 (Edifici Nexus) � 08034 Barcelona
T. 93 205 6464 � F. 93 205 6979 � jprats@cesca.es
......................................................................
next prev parent reply other threads:[~2008-04-02 8:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 22:27 [linux-lvm] LVM Questions Nicholas Muguira
2008-04-02 8:20 ` Jordi Prats [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-29 16:55 [linux-lvm] LVM questions Eric A. Hall
2007-03-29 17:38 ` Stuart D. Gathman
2007-04-20 13:36 ` Nix
2001-05-03 0:48 [linux-lvm] LVM Questions Darren Young
2001-05-03 1:26 ` Glenn Shannon
2001-05-03 1:45 ` Evan Day
2001-05-03 6:56 ` Adrian Phillips
2001-05-04 9:33 ` Heinz J. Mauelshagen
2001-05-04 7:45 ` Adrian Phillips
2001-05-04 10:38 ` Heinz J. Mauelshagen
2001-05-04 9:38 ` Adrian Phillips
2001-05-04 13:39 ` Heinz J. Mauelshagen
2001-05-03 11:15 ` Heinz J. Mauelshagen
2001-05-03 11:41 ` Carlo Marcelo Arenas Belon
2001-05-04 1:59 ` Mark van Walraven
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=47F341B2.2080100@cesca.es \
--to=jprats@cesca.es \
--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).