2.6.10, lockup on lvrename of a snapshot volume

2.6.10, lockup on lvrename of a snapshot volume

[Andre Tomt]

device-mapper snapshots lock up the kernel if you lvrename the snapshot 
volume. The original volume has to be mounted for this to happen.

pvcreate /dev/hdb1
vgcreate testvg /dev/hdb1
lvcreate -L10G -n test testvg
mke2fs -j /dev/mapper/testvg-test
mount /dev/mapper/testvg-test /mnt

lvcreate -s -l 128 -n test_backup testvg/test
lvrename testvg test_backup test_backup.tmp
<lockup>


SysRq Trace of lvrename:
dm_unplug_all [dm_mod]
io_shedule
sync_buffer
sync_buffer
__wait_on_bit
out_of_line_wait_on_bit
sync_buffer
wake_bit_function
wake_bit_function
sync_dirty_buffer
ext3_unlockfs [ext3]
thaw_bdev
__unlock_fs [dm_mod]
dm_resume [dm_mod]
do_resume [dm_mod]
dev_suspend [dm_mod]
ctl_ioctl [dm_mod]
sys_ioctl
syscall_call

LVM2 version is 2.00.24 (Debian Sarge userland), kernel 2.6.10 from 
kernel.org. It has been reported that this affects 2.6.9 also, but I 
have not verified this myself.

Re: 2.6.10, lockup on lvrename of a snapshot volume

[Martin Hermanowski]

[-- Attachment #1: Type: text/plain, Size: 609 bytes --]

On Sat, Dec 25, 2004 at 04:16:08PM +0100, Andre Tomt wrote:
> device-mapper snapshots lock up the kernel if you lvrename the snapshot 
> volume. The original volume has to be mounted for this to happen.
[...]
> LVM2 version is 2.00.24 (Debian Sarge userland), kernel 2.6.10 from 
> kernel.org. It has been reported that this affects 2.6.9 also, but I 
> have not verified this myself.

I experienced the same with 2.6.9-rc2-mm4 (also running Sarge). The
system runs fine, but the lvrename process gets stuck and the lvm
subsystem isn't working properly after, a reboot is required.

LLAP, Martin

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]