Re: [PROBLEM] Device-mapper snapshot metadata userspace breakage

Pekka J Enberg <[email protected]> wrote:
>
> The commit aa14edeb994f8f7e223d02ad14780bf2fa719f6d "[PATCH] device-mapper 
>  snapshot: load metadata on creation" breaks userspace and is blocking us 
>  from moving to the 2.6.16 series kernel. Debian doesn't have the 
>  new required LVM version in stable yet. Is the change intentional?

The changelog said

  If you're using lvm2, for this patch to work properly you should update
  to lvm2 version 2.02.01 or later and device-mapper version 1.02.02 or
  later.

Which was pretty bad of us.  I hope LVM 2.02.01 userspace is
back-compatible with older kernels?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PROBLEM] Device-mapper snapshot metadata userspace breakage
    • From: Pekka J Enberg <[email protected]>

• References:
  • [PROBLEM] Device-mapper snapshot metadata userspace breakage
    • From: Pekka J Enberg <[email protected]>

• Prev by Date: [patch] raid5_unplug_device() fix
• Next by Date: [Patch: 000/006] pgdat allocation for new node add
• Previous by thread: [PROBLEM] Device-mapper snapshot metadata userspace breakage
• Next by thread: Re: [PROBLEM] Device-mapper snapshot metadata userspace breakage
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]