Demi Marie Obenour

> 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...

> Defragmentation might involve multiple transactions if a destination block is occupied, which is beyond the scope of the tools. This is somewhat disappointing. I was hoping for a tool...

> To that end we're currently working on a new iteration of thin that uses variable size blocks and will perform *much* better. Would it be possible to also fix...

Will it be possible to migrate old pools to the new format? Also, I must say that being able to use a 256-bit hash as the thin device ID would...

> To that end we're currently working on a new iteration of thin that uses variable size blocks and will perform *much* better. I'm also not considering enhancements to the...

> no Do you have any idea when it will be made available (e.g. on dm-devel)?

Which of the following (if any) do you plan to support in dm-thin v2? - User-provided per-thin metadata - Being able to assign names to thin volumes, instead of numbers...

To be clear: this is a big list and I do not expect you to add support for every one of these features, _especially_ in the initial patchset. That said,...

> > Which of the following (if any) do you plan to support in dm-thin v2? > > > > - User-provided per-thin metadata > > No Understandable, if disappointing....

To elaborate regarding discard: I would like `blkdiscard` on a thin device to take time proportional to the number of unshared blocks, not the total number of provisioned blocks.