-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Neil Bothwick wrote: > On Tue, 06 Nov 2007 00:18:47 -0500, Eric S. Johansson wrote: > >> if I remember correctly, and it has been quite a while, vgscan >> only works if your lvm.conf is intact. > > You remember incorrectly. lvm.conf is not needed to use LVM. It > configures some aspects of LVM, such as filtering out devices to > speed up scanning and setting snapshot policies, but it is not > needed to access the data on the LVM volumes. > > The only time I have had a problem accessing the data from an LVM > on a different machine is when both systems used the same volume > group name, which is solved by renaming one of them. > > I had a laptop running LVM and then the BIOS told me to backup my data because my drive was going to die. I pulled the drive, popped it into a USB enclosure and brought it to my desktop to rsync it to an eSATA drive. All I had to do was vgscan and vgchange -a y and I was up and running. Actually, I too had a problem with my VG's named the same thing. It wasn't a problem to access different LV's but I changed the VG anyway. As a pointer for people, you might want to append the name of your box to your VG, that way it will be (probably) unique on your network. Also you'll know where you are if you need to do a backup like I had to.
Eric -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHMFjqaiVxdKlBO58RAlXbAJwM7m2wmF9FoLfZFRHVqWScypKI8QCfSHfU YVgvyOkz37lavC8MKSjZtMY= =fBa1 -----END PGP SIGNATURE----- -- [EMAIL PROTECTED] mailing list
