Re: How to check if thin volume or snapshot was ever activated

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

 



On Sat, Aug 7, 2021 at 7:43 PM Gionatan Danti <g.danti@xxxxxxxxxx> wrote:
>
> Dear all,
> as you know, a thin snapshot does have the "k" (skip activation) flag
> set, so one has to force activation by ignoring the flag (or removing
> the flag itself).
>
> I wonder: can we detect if a volume/snapshot was *ever* activated? My
> reasoning is that a never-activated snapshot surely did not receive any
> application writes, so it can be safely removed (ignoring snapshot
> retention policy).

It sounds like you intend to keep snapshots that have been updated
(written) since its creation, right?
The precise way might be checking the data mappings via thin_dump. An
updated device has data mappings with timestamps greater than the
device's creation time.

Checking device activation might not meet what you need. An activated
device might or might not receive any write, so you don't know whether
a device has been updated by looking into its activation history.

_______________________________________________
linux-lvm mailing list
linux-lvm@xxxxxxxxxx
https://listman.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/




[Index of Archives]     [Gluster Users]     [Kernel Development]     [Linux Clusters]     [Device Mapper]     [Security]     [Bugtraq]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]

  Powered by Linux