questions on FILE_INTERNAL_INFORMATION.IndexNumber

NTFSD
1

Hello,
Can anyone tell me if the IndexNumber identifier returned for a
FileInternalInformation file information query is:

a) guaranteed to be unique on a given volume for both files and directories
b) can a file or directories IndexNumber change over time? If so, what
circumstances will change it.

Thanks,
Joel

2

questions on FILE_INTERNAL_INFORMATION.IndexNumber1) Volume unique
2) It will not change
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Smith, Joel
Sent: Friday, April 21, 2000 7:44 AM
To: File Systems Developers
Subject: [ntfsd] questions on FILE_INTERNAL_INFORMATION.IndexNumber

Hello,
Can anyone tell me if the IndexNumber identifier returned for a
FileInternalInformation file information query is:

a) guaranteed to be unique on a given volume for both files and
directories
b) can a file or directories IndexNumber change over time? If so, what
circumstances will change it.

Thanks,
Joel

3

questions on FILE_INTERNAL_INFORMATION.IndexNumber>Subject: [ntfsd] RE:
questions on >FILE_INTERNAL_INFORMATION.IndexNumber

  1. Volume unique
  2. It will not change

Sorry, but what on FAT defragmentation? FAT (unlike NTFS) do not have a
concept of the “file number” like inode number in UNIX. So, FASTFAT uses
the following:

// Extract the data and fill in the non zero fields of the
output
// buffer. We use the logical offset of the dirent describing
// this file on the volume.
//

Buffer->IndexNumber.LowPart =
( NodeType(Fcb->ParentDcb) != FAT_NTC_ROOT_DCB ?
FatGetLboFromIndex( Fcb->Vcb,
Fcb->ParentDcb->FirstClusterOfFile ) :
Fcb->Vcb->AllocationSupport.RootDirectoryLbo ) +
Fcb->DirentOffsetWithinDirectory;

The offset they use is clearly a subject to change on defragmentation.

Max