Removing a disk from the system
Quoted 15 lines · Torsten Landschoff
Hi *,
Today I learned something about LVM the hard way. We are still using 0.8i with 2.2.19 over here since I had nothing but problems with 0.8 and 0.9beta2 (or which beta it was). (The problems were already reported on this list so I chose to do nothing about it).
Now today I replaced a disk in the server being the only PV of the VG data. Simple thing: Install the next disk, add it to the VG and pvmove the data over to it, then remove the old PV.
Then I took out the old disk and jumpered the new one as master. As expected I got an error message from LVM on reboot - I should run vgscan.
Quoted 6 lines
I then ran vgscan to get the vg activated again but killed my other volume group!? I spent hours to get it working again but finally figured to jumper the new disk as slave again, vgexport the VG and import it again after setting it to master.
Seems like I should have used vgexport/import in the first time.
Actually not.
vgscan *should* have cut it.
It would be rather helpful, if you could provide the VGDA of the problematic configuration and the vgscan output with option "-d" in order to investigate searching for any bugs better.
In case you are able to reproduce the situation, where vgscan just finds one but not both of the VGs, please send that data to me.
BTW: jou can provide the VGDA copy by:
dd if=/dev/hdWhatever bs=1k count=4000 | bzip2 > vgda
Quoted 5 lines
Anyway,
now I am wondering what will happen if we need to replace a disk since it starts to die or something along that line? pvmoving the data is no problem, but what can I do if the disk fails before I can do anything?
The only way around such hardware flaws or failures is to set up disk redundancy.
You can achive that using Linux MD, configure RAID1 or RAID5 sets and use those as LVM PVs *or* you could go for hardware raid subsystems.
Quoted 3 lines
IOW: Is the problem I ran into a problem by design or is it a bug in the 0.8i LVM?
See my above request.
Quoted 7 lines
cu
Torsten
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
Signature · 15 lines
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
[email protected] +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-Quoted 4 lines · Heinz J. Mauelshagen
Quoted 1 line
Seems like I should have used vgexport/import in the first time.
Actually not.
vgscan *should* have cut it.
Thanks, so I did not do anything wrong. Of course given that the data is still there it seems I was at least careful enough ;)
Quoted 6 lines
It would be rather helpful, if you could provide the VGDA of the problematic configuration and the vgscan output with option "-d" in order to investigate searching for any bugs better.
In case you are able to reproduce the situation, where vgscan just finds one but not both of the VGs, please send that data to me.
Of course that system is again running production and I guess to reproduce the problem I had to switch disks once again. I guess the real problem was that /dev/hdb1 became /dev/hda1 after removing the old disk.
I'll try to reproduce the problem at my home machine but I can't promise anything.
Greetings
Torsten
Quoted 13 lines · Torsten Landschoff
Quoted 4 lines · Heinz J. Mauelshagen
Quoted 1 line
Seems like I should have used vgexport/import in the first time.
Actually not.
vgscan *should* have cut it.Thanks, so I did not do anything wrong. Of course given that the data is still there it seems I was at least careful enough ;)
Quoted 4 lines
It would be rather helpful, if you could provide the VGDA of the problematic configuration and the vgscan output with option "-d" in order to investigate searching for any bugs better.
Quoted 6 lines
Quoted 2 lines
In case you are able to reproduce the situation, where vgscan just finds one but not both of the VGs, please send that data to me.
Of course that system is again running production and I guess to reproduce the problem I had to switch disks once again. I guess the real problem was that
/dev/hdb1became/dev/hda1after removing the old disk.
Configuration changes in io pathes is a major thing vgscan addresses. I'm very much interested in every bug in this area.
Quoted 3 lines
I'll try to reproduce the problem at my home machine but I can't promise anything.
Ok.
Thank you.
Quoted 8 lines
Greetings
Torsten
_______________________________________________
linux-lvm mailing list
[email protected]
http://lists.sistina.com/mailman/listinfo/linux-lvm
Signature · 15 lines
Regards,
Heinz -- The LVM Guy --
*** Software bugs are stupid.
Nevertheless it needs not so stupid people to solve them ***
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Heinz Mauelshagen Sistina Software Inc.
Senior Consultant/Developer Am Sonnenhang 11
56242 Marienrachdorf
Germany
[email protected] +49 2626 141200
FAX 924446
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-