On Fri, 2008-06-06 at 08:29 +0200, Milan Broz wrote: > ross@biostat.ucsf.edu wrote: > >> I did some expanding and shrinking of my volumes and then attempted to > >> take a snapshot. I got an error message that started "Invalid LV in > >> extent map". I now see that message when I do lvscan or pvscan as well. > >> > >> This looks very bad, and seems to be the same situation as described here: > >> http://weblog.pell.portland.or.us/~orc/2008/02/20/000/index.html > > And where did you send bugreport for that problem? > > ok, it seems that we have already one > > https://bugzilla.redhat.com/show_bug.cgi?id=209927 > > Should be fixed in LVM2 2.02.36. > > Milan > -- > mbroz@redhat.com Excellent! Is that a kernel level or userspace fix? How do I know if I've got it? Currently lvm version says LVM version: 2.02.35 (2008-04-15) Library version: 1.02.24 (2007-12-20) Driver version: 4.12.0 The bug indicates that converting to LVM2 will fix things. I have no reason to stick with LVM1, so that may be the best way to go. Are there any gotcha's? Can vgconvert be run while the volumes and group are in use? Thanks. Ross _______________________________________________ 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/
