The Precise Pangolin has reached end of life, so this bug will not be
fixed for that release
** Changed in: lvm2 (Ubuntu Precise)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
** Also affects: lvm2 (Ubuntu Precise)
Importance: Undecided
Status: New
** Changed in: lvm2 (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: lvm2 (Ubuntu Precise)
Status: New => Confirmed
** Changed in: lvm2 (Ubuntu Precise)
Importance: Undecided => Low
--
See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660839
and
from ftp://sources.redhat.com/pub/lvm2/WHATS_NEW
Version 2.02.89 - 26th January 2012
===
...
Replace :space: with [\t ] for awk in vgimportclone (not widely supported).
12.04 LTS still uses 2.02.66
I have just had the same problem on a fully updated 12.04 LTS box. I
scratched around and discovered that vgimportclone is a shell script
that makes a temporary copy of your lvm.conf and sets up a filter in
that custom config so as to only operate on the physical volumes you
specify on the command
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lvm2 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695759
Title:
vgimpo
I just got hit by this bug too. On a fully patched Ubuntu Server
10.04.4 LTS box, I used vgimportclone and it renamed a different volume
group than I asked it to, leaving me with an unbootable system until I
was able to rename the volume group back.
--
You received this bug notification because