Messages in this thread | | | Date | Sat, 25 Dec 2004 16:16:08 +0100 | From | Andre Tomt <> | Subject | 2.6.10, lockup on lvrename of a snapshot volume |
| |
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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |