Martin K. Petersen wrote: > At the Filesystem & Storage Workshop there was lots of discussion > about how to communicate I/O alignment, stripe width, etc. to the > filesystems so they could lay out things properly. That's really nice, thanks. Does it handle devices with different properties in differeng offset ranges? E.g. a RAID setup where the first 100GB have one stripe width, but the next 100GB have a different stripe width - as you can get if you join two different hardware RAIDs with LVM, for example. > The physical sector offset for the start of the "virtual" block device > is also exported. This includes partitions so you can get the actual > physical start sector offset for - say - an MD device sitting on a > partitioned set of drives. If it's a set of drives, doesn't it need to return multiple offsets, and drive identities? > Comments and suggestions are welcome. >From a database perspective, I'm thinking it would be very useful to provide similar information for large files. Database engines have the same requirement to know stripe width etc., and filesystems allocate large contiguous extents so it it makes sense to pass the device characteristics up to the app, with appropriate offset. (Same for loopback devices.) This is an extreme example of different properties in different offset ranges - it depends on file allocation. Is there scope to extend FIEMAP to pass this sort of information? -- Jamie -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
