On Wed, Feb 07, 2007 at 12:35:32AM +0100, Marc Lehmann wrote:
it's just not release-critical, as you suggested in your bug severity.
I never suggested it was release-critical. reportbug suggested to use
critical because:
1 critical makes unrelated software on the system (or the whole
On Mon, Feb 05, 2007 at 04:44:23PM +0100, Marc Lehmann wrote:
On Fri, Feb 02, 2007 at 08:16:38PM -0800, Steve Langasek [EMAIL PROTECTED]
wrote:
According to #383418, this bug only affects versions of libdevmapper1.02
previous to the version currently in etch, and there is no
On Tue, Feb 06, 2007 at 03:25:35PM -0800, Steve Langasek [EMAIL PROTECTED]
wrote:
(no kill -9), which cannot be a userspace problem unless you assume
libdevmapper opens /dev/mem and pokes into the kernel directly.
Ok, that's fair, it's a kernel bug for allowing such a deadlock to occur;
On Fri, Feb 02, 2007 at 08:16:38PM -0800, Steve Langasek [EMAIL PROTECTED]
wrote:
According to #383418, this bug only affects versions of libdevmapper1.02
previous to the version currently in etch, and there is no libdevmapper1.02
in sarge. There is a libdevmapper1.01, but it's not clear that
Package: linux-image-2.6.18-4-amd64
Version: 2.6.18.dfsg.1-9
Severity: critical
Justification: causes serious data loss
I just upgraded to 2.6.18.4 and tried pvmove /dev/hdc1 /dev/sda1
Result (dmesg):
device-mapper: mirror log: unrecognised sync argument to mirror log: 2
device-mapper:
severity 409435 important
thanks
On Sat, Feb 03, 2007 at 03:21:31AM +0100, Marc Lehmann wrote:
I just upgraded to 2.6.18.4 and tried pvmove /dev/hdc1 /dev/sda1
Result (dmesg):
device-mapper: mirror log: unrecognised sync argument to mirror log: 2
device-mapper: table: 254:3: mirror:
6 matches
Mail list logo
