> Just to clarify, this means that the "inode numbers" reported by an
> msdos filesystem are a function of the disk-layout itself (i.e. they
> are determined at mount time), and not numbers created when the file
> is first accessed (AFAIK).
Wrong. open file. rename() it to another directory. truncate it to
zero. write to it. ->i_ino must have stayed they same. _Nothing_
on-disk that would be related to that file had stayed the same.
FAT simply doesn't allow inode numbers as functions of disk layout.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/