| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Neil Bothwick wrote: |
| 5 |
> On Tue, 06 Nov 2007 00:18:47 -0500, Eric S. Johansson wrote: |
| 6 |
> |
| 7 |
>> if I remember correctly, and it has been quite a while, vgscan |
| 8 |
>> only works if your lvm.conf is intact. |
| 9 |
> |
| 10 |
> You remember incorrectly. lvm.conf is not needed to use LVM. It |
| 11 |
> configures some aspects of LVM, such as filtering out devices to |
| 12 |
> speed up scanning and setting snapshot policies, but it is not |
| 13 |
> needed to access the data on the LVM volumes. |
| 14 |
> |
| 15 |
> The only time I have had a problem accessing the data from an LVM |
| 16 |
> on a different machine is when both systems used the same volume |
| 17 |
> group name, which is solved by renaming one of them. |
| 18 |
> |
| 19 |
> |
| 20 |
I had a laptop running LVM and then the BIOS told me to backup my data |
| 21 |
because my drive was going to die. I pulled the drive, popped it into |
| 22 |
a USB enclosure and brought it to my desktop to rsync it to an eSATA |
| 23 |
drive. All I had to do was vgscan and vgchange -a y and I was up and |
| 24 |
running. Actually, I too had a problem with my VG's named the same |
| 25 |
thing. It wasn't a problem to access different LV's but I changed the |
| 26 |
VG anyway. As a pointer for people, you might want to append the name |
| 27 |
of your box to your VG, that way it will be (probably) unique on your |
| 28 |
network. Also you'll know where you are if you need to do a backup |
| 29 |
like I had to. |
| 30 |
|
| 31 |
Eric |
| 32 |
-----BEGIN PGP SIGNATURE----- |
| 33 |
Version: GnuPG v1.4.7 (GNU/Linux) |
| 34 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
| 35 |
|
| 36 |
iD8DBQFHMFjqaiVxdKlBO58RAlXbAJwM7m2wmF9FoLfZFRHVqWScypKI8QCfSHfU |
| 37 |
YVgvyOkz37lavC8MKSjZtMY= |
| 38 |
=fBa1 |
| 39 |
-----END PGP SIGNATURE----- |
| 40 |
|
| 41 |
-- |
| 42 |
gentoo-user@g.o mailing list |
Archives