[Bug 1480923] Re: lvm thin corruption after lvresize

Peik pakezonite at gmail.com
Wed May 4 13:11:12 UTC 2016


Hi!

I'm not sure but this might be somehow related:
http://askubuntu.com/questions/758693/using-lvm-and-thin-provisioning-thinpool-on-a-pv-larger-than-2t

Just thought the thin pool size being over 2T might have something to do
with it...

Also, I don't know if increasing the pool size automatically also increases the pool metadata portion so you might 
want to check that so you're not running out.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1480923

Title:
  lvm thin corruption after lvresize

Status in lvm2 package in Ubuntu:
  New

Bug description:
  lvm2 version 2.02.98-6ubuntu2

  After doing a lvresize of a LVM Thin Pool, I had a corruption all sub
  LVM Thin Volumes and lost all of them. Then tried to dump/repair the
  tmeta and end up with empty thin volumes (no more filesystem signature on them).

  To sum up
  The thin_pool was 2T and I tried to increased it to 3T...

  As fare as I know, none of the partitions were full but I increased the main
  thin pool as it was close to the sum of all sub thin volumes.

  I assume that using LVM Thin is still not stable on 14.04 LTS right?

  I guess that lvm2 2.02.98 does not properly handle the metadata resize
  of a thin pool right? (maybe add a warning somewhere in doc?)

  Maybe related to
  http://comments.gmane.org/gmane.linux.kernel.device-mapper.devel/19190
  https://www.redhat.com/archives/lvm-devel/2013-June/msg00371.html

  I managed to recover some files from the raw thin_pool (tdata/tpool) with scalapel
  but that is it.

  Do you known any other tools to recovery lvm thin volumes or
  partition/data on it?

  Errors

    attempt to access beyond end of device
    dm-6: rw=0, want=7753528, limit=262144
    attempt to access beyond end of device
    dm-6: rw=0, want=7753528, limit=262144
    attempt to access beyond end of device
    dm-6: rw=0, want=7753528, limit=262144
    attempt to access beyond end of device
    dm-6: rw=0, want=7753528, limit=262144

    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 2199023190016: Input/output error
    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 2199023247360: Input/output error
    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 0: Input/output error
    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 4096: Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 805306302464: Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 805306359808: Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 0: Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 4096: Input/output error

  lvs
    LV             VG     Attr      LSize   Pool      Origin Data%  Move Log Copy%  Convert
    thin_archive   mainvg Vwi-aotz- 500.00g thin_pool         94.65
    thin_rsnapshot mainvg Vwi-aotz-   1.50t thin_pool         94.01
    thin_pool      mainvg twi-a-tz-   3.00t                   71.65

  lvresize -L 2T /dev/mapper/mainvg-thin_rsnapshot
    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 1649267376128: Input/output error
    /dev/mainvg/thin_rsnapshot: read failed after 0 of 4096 at 1649267433472: Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 536870846464: Input/output error
    /dev/mainvg/thin_archive: read failed after 0 of 4096 at 536870903808: Input/output error
    Extending logical volume thin_rsnapshot to 2.00 TiB
    Logical volume thin_rsnapshot successfully resized

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1480923/+subscriptions



More information about the foundations-bugs mailing list