>We are about to start implementing a fs where data can move around the >device and so a physical block address is not really useful. I have >understood from other postings to this list that reiserfs and ntfs >don't implement this method so I suppose we'll do the same. I'll just >find some nice error to return.
It's appropriate only for the most classic of filesystems, really. It was always a layering violation, but is handy for hackish things. Interfaces that expose block addresses are in the same boat as all those fsstat fields -- block size, blocks used, blocks free, inodes used, inodes free. They make sense for the original Unix File System, but get harder to give meaning with every new generation. -- Bryan Henderson IBM Almaden Research Center San Jose CA Filesystems - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
