bin/47263: lvm: lvrename breaks things.

[riz%NetBSD.org@localhost]

>Number:         47263
>Category:       bin
>Synopsis:       'lvm lvrename' destroys working logical volume
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    bin-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Nov 29 19:40:00 +0000 2012
>Originator:     Jeff Rizzo <riz%NetBSD.org@localhost>
>Release:        NetBSD 6.0_BETA (March 10, 2012)
>Organization:
        
>Environment:
        
        
System: NetBSD xenserver1.boogers.sf.ca.us 6.0_BETA NetBSD 6.0_BETA (XEN3_DOM0) 
amd64
Architecture: x86_64
Machine: amd64
>Description:
        I renamed a working logical volume thusly:

        sudo lvm lvrename mirror/BASE mirror/BASE-6-amd64

        ...and it appeared to work.  However, when I went to use the
volume in question, I got errors:

xenserver1:riz  ~> sudo mount /dev/mapper/mirror-BASE--6--amd64 /altroot 
mount_ffs: /dev/mapper/mirror-BASE--6--amd64 on /altroot: incorrect super block
xenserver1:riz  ~> sudo fsck /dev/mapper/mirror-BASE--6--amd64 
** /dev/mapper/rmirror-BASE--6--amd64
fsck: /dev/mapper/rmirror-BASE--6--amd64: Floating point exception
xenserver1:riz  ~> sudo dumpfs /dev/mapper/rmirror-BASE--6--amd64 
dumpfs: /dev/mapper/rmirror-BASE--6--amd64: could not find superblock, skipped
xenserver1:riz  ~>

Thinking something else had screwed it up, I attempted to restore the data:

xenserver1:riz  ~> xzcat /tmp/NetBSD-6.0-amd64.xz| sudo dd 
of=/dev/mapper/rmirror-BASE--6--amd64 bs=1m
dd: /dev/mapper/rmirror-BASE--6--amd64: end of device
0+1 records in
0+0 records out
0 bytes transferred in 0.001 secs (0 bytes/sec)
xenserver1:riz  ~> 

>How-To-Repeat:
        Have a working 1G logical volume.  Rename it using 'lvm lvrename',
and watch it be broken.

>Fix:
        none given.