From: Randy Katz <rkatz@simplicityhosting.com>
To: linux-lvm@redhat.com
Subject: Re: [linux-lvm] drive crash question
Date: Tue, 08 Mar 2011 19:43:55 -0800 [thread overview]
Message-ID: <4D76F77B.3030303@simplicityhosting.com> (raw)
In-Reply-To: <4D76ED00.1050305@simplicityhosting.com>
nevermind, brought new os/drive up with drive1, ran lvscan and they are
all there!
I love LVM! Wish everything else would work as well!
On 3/8/2011 6:59 PM, Randy Katz wrote:
> Hi,
>
> My main system drive crashed. The second drive (drive1) was pd0 with
> vg1 and logical volumes
> in operation. If I replace the drive0 will a vgscan and lvdisplay
> automatically "see" the volumes
> on the drive or is there something that must be done first?
>
> Thank you in advance,
> Randy
>
> _______________________________________________
> 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/
>
prev parent reply other threads:[~2011-03-09 3:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 2:59 [linux-lvm] drive crash question Randy Katz
2011-03-09 3:43 ` Randy Katz [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=4D76F77B.3030303@simplicityhosting.com \
--to=rkatz@simplicityhosting.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).