Thanks for your reply, I found the the following thing interesting on its own:
On 4/7/05, Nikita Danilov <[EMAIL PROTECTED]> wrote: > Consider tools like LILO that want stable block numbers for certain > files. In reiserfs (both v3 and v4) there is an ioctl that disables > relocation for a given file. Besides, I do not think ->bmap() is useless > even when block numbers are volatile, for one thing it allows user level > to track how file is laid out (for example, to measure fragmentation). I tried to google out what behaviour lilo requires filesystems to exhibit without much success... is that information available somnewhere I din't look? Is that simple enought to be explained here? TIA Martin - 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
