On Wed, Feb 11, 2015 at 11:13:38AM -0500, Trond Myklebust wrote: > I'm wondering if the right way to do READ_PLUS would have been to > instead have a separate function READ_SPARSE, that will return a list > of all sparse areas in the supplied range. We could even make that a > READ_SAME, that can do the same for patterned data. That soudns like the protocol level equivalent of the fiemap ioctl. While fiemap is useful for filesystem debugging, using it for detection of sparse ranges in oreutils turned out to be a desaster, and we instead oved to support lseek SEEK_DATA/SEEK_HOLE, which would map to SEEK in NFSv4.2. The userspace tools use the different in file size vs allocate blocks in the stat data to decide if they use SEEK_DATA/SEEK_HOLE, which should work just fine over NFSv4.2 as well. -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
