Hi Bryn
Just to avoid confusion, this is a different Roland from the original query.
Looking at
http://www.kernel.org/pub/linux/kernel/people/agk/patches/2.6/editing/dm-loop.patch
+ if (!cur_block)
+ goto bad_bmap;
...
+bad_bmap:
+ DMERR("Loopfile has holes");
+ dump_extent_map(map);
Does this mean that dm-loop does not support sparse loop-back files?
Also, it seems that the approach with dm-loop is that you sniff the (current?) file mapping onto its underlying block device. What happens if the loopback file is modified, or the file system hosting the loopback file does some re-arranging? (I might be way off-tack here - this was a first impression of the code).
I'd be interested in comparing dm-loop to vanilla loop which we currently use.
Regards
Roland #2
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
