Hi, I found an interesting behavior when I was debugging my dm-writeboost. device-mapper splits in-coming bio into small bios called clone bio and target writes "how to handle a clone bio". There is end_io method which is called in clone_endio. That should be called when the clone bio is acked by underlying device. My expectation is clone bio payload is always set when it's reached endio function, as well as ordinary bio. payload is set means bi_sector is set and bvecs are filled with data. But my expectation is betrayed. I found there is a condition to reproduce this. It's whether the underlying device is also wrapped by linear target or not. When it's wrapped by linear target, the clone bio's payload is somehow set. Otherwise not. Precisely, dm-writeboost requires backing store and caching device as underlying devices. And I expect the read clone bio acked by backing store should be payload set. But it's not, when the backing store is raw HDD rather than linear device backed by a HDD. I post this because I wonder whether this is device-mapper limitation or just a bug. Thanks, Akira -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
