From: "Chad C. Walstrom" <chewie@wookimus.net>
To: linux-lvm@sistina.com
Subject: Re: [linux-lvm] Just for information ....
Date: Tue Nov 20 15:36:01 2001 [thread overview]
Message-ID: <20011120153717.G9141@wookimus.net> (raw)
In-Reply-To: <20011120214104.A24005@cistron.nl>
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
On Tue, Nov 20, 2001 at 09:41:04PM +0100, Wichert Akkerman wrote:
> Previously Andreas Dilger wrote:
> > Yes. You will need to do a vgscan to find the new disks. Hopefully they
> > will not have the same VG name as another VG on that system.
>
> What if they do?
Nothing, originally. Your last "vgchange -a y" should populate the
/etc/lvmtab.d directory with the current working volume group data.
Even if you have two vg's of the same name, your last one should be the
active one.
I had to go back to the original system and do a vgexport <vgname> in
order to import it on the new system. I've considered naming vg's after
their host (and possibly media type). That way, I'll know I have at
least a stub of a unique name for the vg.
As far as keeping VG's separate based on media... I'm torn. It's a
simple way of making sure I don't loose data if the IDE disk goes bad --
which has happened to me -- while the SCSI disk remains fine.
Unless I'm using RAID, grouping multiple physical disks together in one
VG means I have to pay extra special attention to where the LV's
allocate their PE's.
--
Chad Walstrom <chewie@wookimus.net> | a.k.a. ^chewie
http://www.wookimus.net/ | s.k.a. gunnarr
Key fingerprint = B4AB D627 9CBD 687E 7A31 1950 0CC7 0B18 206C 5AFD
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2001-11-20 15:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-20 12:39 [linux-lvm] Just for information Igor Dumaire
2001-11-20 13:55 ` Andreas Dilger
2001-11-20 14:39 ` Wichert Akkerman
2001-11-20 15:36 ` Chad C. Walstrom [this message]
2001-11-20 16:05 ` Andreas Dilger
2001-11-23 6:07 ` Heinz J . Mauelshagen
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=20011120153717.G9141@wookimus.net \
--to=chewie@wookimus.net \
--cc=linux-lvm@sistina.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