Ming-Hung Tsai

The equation in cache_metadata_size assumes the mappings and hints are stored in btrees rather than arrays: The `BYTES_PER_BLOCK` denotes the 16-byte key & value for each cache block, and the...

The random seed for `SmallRng` is 128-bit on 32-bit platforms, and 256-bit on 64-bit platforms (for PRNGs `Xoshiro128PlusPlus` and `Xoshiro256PlusPlus`, respectively). I would prefer this way: ``` diff --git a/src/write_batcher/tests.rs...

You're using a wrong input. The pool metadata volume for PVE should be `/dev/mapper/pve-data_tmeta`, so here's what you need: ``` lvchange -ay pve/data_tmeta thin_dump --repair /dev/mapper/pve-data_tmeta ``` It's also recommended...

Could you activate the pool metadata device read-only? e.g., `lvchange -ay vg1/tp1_tmeta`, then you're able to run thin_check on the metadata device (`thin_check /dev/mapper/vg1-tp1_tmeta`) to see what happenn.

> does the blk-archive script allow also restoring to a clean new block device after doing a vgcfgrestore? Yes, blk-archive helps imaging thin devices, and you can restore archived thin-devices...

Be aware that the component LVs might be virtual targets (targets that are not map to PV directly), e.g., cache, writecache, or raid. You should handle those target types with...

Sorry for the inconvenience. It's because the v1.0.9 tag was moved from commit ce1c85c2 to 1d60839 in a short while. I believe there should be a 1.0.9-2 release for Arch...

Does Rust now handle 64-bit offsets in 32-bit builds? I use stat64 explicitly as a workaround (commit 775c33269bf)

Thank you for reporting this issue. The regression originated in v1.0.5 due to the clap dependency update. I’ll fix it shortly.

I would prefer keep using the std AtomicU64. Let me think about it.