how many instances of e are there in:
q: can lvms pvmove command skip extents that have never held data? i am using pvmove to migrate lvm extents from one pv to another. it works like it should, however, the physical volumes are actually thin provisioned disks from two separate storage arrays. both disks are 20g (5119 lvm extents), but the source disk had only 5gb of stored data on the storage array. after pvmove is finished, the destination disk has 20gb used on the second storage array, eliminating the benefit of thin provisioning.
can pvmove be instructed to only copy the extents that have ever had data written to them? does lvm even have that info, or is it just a side effect of the storage array allocating space on demand?

a: some high end storage arrays are clever enough to see that the block is empty, and just acknowledge the io to the system without actually filling up the thin pool. your array does not seem to be concerned.
you have 2 options to workaround your issue :
1/ use the fstrim command to give back unused blocks to the storage array (kind of post processing, when you launch the command)
2/ mount your filesystems with the -o discard option (live processing). as soon as you delete a file (big enough), the block is given back to the array.

user
The text includes 113 "e"s in total.
assistant