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

Bug#409435: linux-image-2.6.18-4-amd64: old version of libdevmapper1.02 installed == eat filesystem on pvmove



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: Error creating mirror dirty log
>    device-mapper: ioctl: error adding target to table
>    device-mapper: mirror log: unrecognised sync argument to mirror log: 2
>    device-mapper: table: 254:3: mirror: Error creating mirror dirty log
>    device-mapper: ioctl: error adding target to table
>    device-mapper: table: device 254:3 too small for target
>    device-mapper: table: 254:1: linear: dm-linear: Device lookup failed
>    device-mapper: ioctl: error adding target to table

> and the volume was inaccessible. after a pvmove --abort, the whole system
> hang.

> after reboot, the files and whole directories were missing, the filesystem
> was corrupted.

> After some digging around, this seems to have been reported
> some time ago and seems to be caused by an old version of
> libdevmapper1.02 (#383418). Unfortunately, the bug was closed.

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 version of
the lib is also affected.

> indeed, upgrading it made pvmove seemingly work (neither upgrading dmsetup
> nor lvm2 upgrades this library to the required version). I think I had
> 1.02.06-1 and upgraded to 1.02.12-1.

> Please, I urge you, add an antidependency to the kernel against old and
> incompatible versions of libdevmapper. This problem is *severe*, causes
> serious data loss, is a known issue, and is so easily avoidable and so
> hard to diagnose.

But it's not a bug in the kernel -- it's a bug in an obsolete, never
released, and unsupported version of devmapper.

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
vorlon@debian.org                                   http://www.debian.org/



Reply to: