Hi Gerry, Thursday, May 1, 2008, 22:21:00, Gerry Reno wrote: > At least in the case where the snapshot is read-only (LVM1 default, > LVM2 by config?), if the snapshot is lost, invalid, not removed from > VG prior to reboot, when LVM comes back up it should see this and > immediately know that it can just vgreduce VG --removemissing for > the old snapshot. In the case of rw (no LVM1, LVM2 default), it > should be a user choice and LVM should prompt the user at boot as to > whether to remove this old snapshot so it can attempt to activate > the VG. Unless the user knows that there were non-backup related lvm > mods written during the snapshot (eg: pvmove) then the user will > just answer yes and the system should boot. This is how LVM should > operate in this scenario. I don't think that automatically making changes to the VG is a good idea. Imagine that you have a snapshot on disk mapped from SAN storage array and that becomes temporary unavailable (SAN switch failure or whatever). It would be a bad idea to remove this PV from VG just because it is TEMPORARY unavailable. And how do you distinguish between ram disk and normal disk and if it is totally gone or it is only temp issue? Also if real HDD fails, you don't want to vgreduce it, you want to replace it, vgcfgrestore it and sync it (in case you are using mirroring). Also imagine that you can have also real data on the same PV, not only snapshot. What would help is the ability to activate the VG also with missing PVs, I'm not sure if that is possible in linux LVM. -- bYE, Marki _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
