Re: Snapshot behavior on classic LVM vs ThinLVM

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

 



Zdenek Kabelac schreef op 18-04-2017 12:17:

Already got lost in lots of posts.

But  there is tool  'thin_ls'  which can be used for detailed info
about used space by every single  thin volume.

It's not support directly by 'lvm2' command (so not yet presented in
shiny cool way via 'lvs -a') - but user can relatively easily run this
command
on his own on life pool.


See for usage of


dmsetup message /dev/mapper/pool 0
    [ reserve_metadata_snap | release_metadata_snap ]

and 'man thin_ls'


Just don't forget to release snapshot of thin-pool kernel metadata
once it's not needed...

There are two ways: polling a number through some block device command or telling the filesystem through a daemon.

Remounting the filesystem read-only is one such "through a daemon" command.


Unmount of thin-pool has been dropped from upstream version >169.
It's now delegated to user script executed on % checkpoints
(see 'man dmeventd')

So I write something useless again ;-).

Always this issue with versions...

So Let's see, Debian Unstable (Sid) still has version 168 as does Testing (Stretch).
Ubuntu Zesty Zapus (17.04) has 167.

So for the foreseeable future both those distributions won't have that feature at least.

I heard you speak of those scripts yes but I did not know when or what yet, thanks.

I guess my script could be run directly from the script execution in the future then.

Thanks for responding though, much obliged.

_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.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