>> NTFS has a 48bit 'inode number' (the FILE record number) which
>> lasts until a file is deleted (where deleted = 0 hard links);
>> it can then be reused, but there is also a 16bit 'generation number'
>> (the sequence number in the FILE record) which is incremented when
>> the inode is reused. So it should be easy to do something there.
>
> Aha. Steve, I didn't really look into NTFS driver's guts (mostly since
> it's R/O and thus all, erm, fun with rename()/unlink()/rmdir() went
The NTFS driver has a config option for read-write.
> without touching it). IIRC it's an FFS-derivative with B-trees used
> wherever possible. What are you using for inumbers?
It doesn't look more like FFS than HFS (MacOS filesystem) does.
All metadata resides in files. That includes the inode-like structures,
so there is no need to guess how many files one might want. This is
recursive.
http://www.via.ecp.fr/~regis/ntfs/new/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/