On Tuesday, 5 June 2018 10:14:16 CEST Marian Csontos wrote: > On 06/04/2018 01:50 PM, Dennis Schridde wrote: > > On Tuesday, 15 May 2018 13:15:55 CEST Zdenek Kabelac wrote: > >> To get direct access to metadata - you could use your latest lvm2 > >> 2.02.177 > >> build (or even 'git master'). In these recent versions there is added > >> support to activate directly these 'subLVs'. So with latest lvm2 you > >> can: > >> > >> lvchange -ay vg/lv_cmeta > > > > This command was only successful in LVM 2.02.178-rc1, but failed in > > 2.02.177.> > >> and then you can capture content of this LV via 'dd' into file > >> and compress and attach 'xz' compressed to BZ. > > > > I created a report in bugzilla [4], but since the `cache_cmeta` LV appears > > to contain parts of my personal files, I cannot attach it. However, I > > gained > It definitely should not. _cdata is where fragments you your data are > stored, and _cmeta contains only metadata (e.g. counters and references > to cdata.) > > If there really are fragments of data in _cmeta LV, something must have > gone wrong elsewhere. Thanks for the insight. I attached the first 4890783 bytes (i.e. those before the blocks of seemingly unstructured data, which I saw in `hexdump -C`) of that LV to the bug report [4]. Hopefully it contains enough information to figure out what is broken. [4]: https://bugzilla.redhat.com/show_bug.cgi?id=1585670
Attachment:
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ linux-lvm mailing list linux-lvm@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
