[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#403733: marked as done (kernel hangs when creating more than one lvm snapshot of the same logical volume)

Your message dated Mon, 6 Aug 2007 17:01:09 +0200
with message-id <20070806150109.GF9774@stro.at>
and subject line kernel hangs when creating more than one lvm snapshot of the same logical volume
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--- Begin Message ---
Package: base
Severity: critical

If you create more than one lvm snaptshot of a logical volume the system hangs.
To reproduce this problem use lvcreate to create a logical volume and try to create two
snapshots of this lv. When invoking the second lvcreate the system should hang.
This behavior can be found in some other distros (debian sarge with 2.6, ubuntu, gentoo) 
but not in rhel or suse.
I think this bug is release critical as it is a regression to debian sarge with 

-- System Information:
Debian Release: 4.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)

--- End Message ---
--- Begin Message ---
> I found a solution to "fix" the bug. We are using a xfs filesystem in
> the logical volumes. The script we used to test made an xfs_freeze just
> before snapshotting. This caused an race condition in the kernel,
> because it tries to make a freeze while creating the snapshot. Without
> doing xfs_freeze everything works almost well.


xfs and lvm tradionaly badly mix,
the situation seems to have improved in the latest kernels.


--- End Message ---

Reply to: