LVM and devices
I may be a day late and a dollar short here, but I experienced a problem this morning when I added a new scsi drive to my 2.2.10 system. I know that the os scans for devices when the system boots and assigns device names then. Well this screwed up my volume groups because sda1 is now sdb1, you get the idea nothing new here. I know this has been discussed before.
In AIX new devices are assigned and that's the way it stays unless you manually delete the device and readd it so that when one of your mirred drives gets blown away or you add a drive the assignments are the same (more to it than this but you get the idea). I believe this needs to change in linux before LVM is added to the kernel, life would be much simpler (md is effected by this as well I beleive). LVM does need to be there though, the old way is just that the old way. I don't know how I would live without LVM when you manage over 200 systems. Just my opinion.
add LVM to 2.4 -- YES.
--
Chaos, panic, & disorder - my work here is done.
Quoted 7 lines
I may be a day late and a dollar short here, but I experienced a problem this morning when I added a new scsi drive to my 2.2.10 system. I know that the os scans for devices when the system boots and assigns device names then. Well this screwed up my volume groups because sda1 is now sdb1, you get the idea nothing new here. I know this has been discussed before.
Run vgscan and VGs should be o.k. again.
Quoted 10 lines
In AIX new devices are assigned and that's the way it stays unless you manually delete the device and readd it so that when one of your mirred drives gets blown away or you add a drive the assignments are the same (more to it than this but you get the idea). I believe this needs to change in linux before LVM is added to the kernel, life would be much simpler (md is effected by this as well I beleive). LVM does need to be there though, the old way is just that the old way. I don't know how I would live without LVM when you manage over 200 systems. Just my opinion.
Quoted 2 lines
add LVM to 2.4 -- YES.
Heinz
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Systemmanagement CS-TS T-Nova
Entwicklungszentrum Darmstadt
Heinz Mauelshagen Otto-Roehm-Strasse 71c
Senior Systems Engineer Postfach 10 05 41
64205 Darmstadt [email protected] Germany +49 6151 886-425 FAX-386
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Quoted 1 line · Heinz Mauelshagen
Run vgscan and VGs should be o.k. again.
If your /dev is 16-aligned...Please make sure that device skipping "optimization" is removed before being submitted to Linus!
(although that is a user-space thing that wouldn't actually go to Linus...)
Signature · 3 lines
Ryan Murray ([email protected], [email protected]) Software Designer, Glenayre Technologies Inc. The opinions expressed here are my own.
Quoted 6 lines · Heinz Mauelshagen
Quoted 1 line
Run vgscan and VGs should be o.k. again.
If your /dev is 16-aligned...Please make sure that device skipping "optimization" is removed before being submitted to Linus!
Yes.
As you say it below:
it is a matter of userspace and _not_ kernelland.
So, Linus doesn't have to care.
I've already thrown it away in upcoming 0.8.
Quoted 4 lines
(although that is a user-space thing that wouldn't actually go to Linus...)
Regards,
Heinz
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Systemmanagement CS-TS T-Nova
Entwicklungszentrum Darmstadt
Heinz Mauelshagen Otto-Roehm-Strasse 71c
Senior Systems Engineer Postfach 10 05 41
64205 Darmstadt [email protected] Germany +49 6151 886-425 FAX-386
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-