thin-provisioning-tools
thin-provisioning-tools copied to clipboard
jthornber
I would like to be able to defragment and shrink thin pools. This would be very useful for desktop use-cases such as Qubes OS. This should work even if the...
Dear developers, I have Proxmox running on LVM Thin Pools. As I know now I made many mistakes. I did not monitor or extend poolmetadatasize. I did not backup the...
thin_trim currently needs to run offline, which is quite inconvienent. It would be much more convienent if thin_trim could be used online.
This is really a feature request for the kernel driver, but would it be possible to have faster discards in dm-thin v2? This is causing problems for Qubes OS (QubesOS/qubes-issues#5426).
There are cases where it would be quite useful to be able to compact a thin pool by deduplicating identical blocks while the system is offline.
Hi Joe, Currently, thin_check checks mapping tree and detail tree separately, which cannot check the compatibility of each other. For example, incompatible device IDs, or the data mapping root points...
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973145 I meet the same bug. My thin-provisioning-tools version is 0.9.0. The linux is openEuler. gcc-c++-10.3.1
Hello, I noticed that `era_invalidate` reads the live metadata (superblock) instead of the metadata snapshot when using the `--metadata-snapshot` parameter. The offending code is https://github.com/jthornber/thin-provisioning-tools/blob/main/era/metadata.cc#L45: The `metadata_snap` parameter is not...
I nearly read cache like tools and read the cache_metadata_size.cc with some questions. ``` uint64_t cache_metadata_size_cmd::calc_size(uint64_t nr_blocks, uint32_t max_hint_width) { uint64_t const SECTOR_SIZE = 512; uint64_t const TRANSACTION_OVERHEAD = meg(4);...
Hello I'm trying to recover the lvm-thing metadata after a hardware failure using thin_ll_dump, but I'm getting a segmentation fault while running the following command: `thin_ll_dump /dev/mapper/pve-data_meta0 --device-details-root=128146 --data-mapping-root=12754 -o...
