Ming-Hung Tsai
Ming-Hung Tsai
The patch had already been merged (1e42ed4)
There's an ongoing feature `thin_shrink` written in Rust, which remaps data blocks beyond the new size to the free blocks before. Not sure that's what you're looking for. The tool...
Yes, the tool works offline and the data is moved to unused blocks, so the original data is untouched. You'll need to start over again if the program is terminated...
Defragmentation might involve multiple transactions if a destination block is occupied, which is beyond the scope of the tools. Second, defragment might not be quite useful due to the copy-on-write...
I ran into similar problem before, when I built thin-p tools for AArch64 platforms. The `config.guess` and `config.sub` really need to be updated, in order to support newer platforms and...
Hi, Here's a quick fix for this issue. https://github.com/mingnus/thin-provisioning-tools/commits/2021-10-12-thin-ll-dump-fixes Could you help provide the LVM archives/backups please? They should be stored in `/etc/lvm/archive/` and `/etc/lvm/backup`, so that I could do...
It's the common transaction id mismatch issue that might happen while filling up the pool metadata. You can run `thin_check` first to make a confirmation: (I use the release build...
> Thanks for your help this is the output of the commands, and yes I tried to run lvconvert --repair on the data-hdd (LV). If you had run `lvconvert --repair`...
How about removing the `empty_mapping_` member, and delay the allocation of mapping root in `begin_device()` ? Is there any reason to preserve the `empty_mapping_` tree ?
> But I worry about putting implicit commits in the code. It makes it impossible to reason about a transaction, or have any confidence about what state a rollback will...