* FileIndex in FSCC FileIdFullDirectoryInformation
@ 2019-12-03 3:07 ronnie sahlberg
0 siblings, 0 replies; only message in thread
From: ronnie sahlberg @ 2019-12-03 3:07 UTC (permalink / raw)
To: Interoperability Documentation Help, linux-cifs
Hi Dochelp,
I am looking at MS-FSCC for the FileIdFullDirectoryInformation
responses.
The description of FileIndex is as:
===
FileIndex (4 bytes): A 32-bit unsigned integer that contains the byte
offset of the file within the
parent directory. For file systems in which the position of a file
within the parent directory is not
fixed and can be changed at any time to maintain sort order, this
field SHOULD be set to 0 and
MUST be ignored.<107>
Footnote for <107> is :
===
<107> Section 2.4.18: When using NTFS, the position of a file within
the parent directory is not fixed
and can be changed at any time. Windows 2000, Windows XP, Windows
Server 2003, Windows Vista,
Windows Server 2008, Windows 7, and Windows Server 2008 R2 set this
value to zero for files on
NTFS file systems.
Is this list of OSs where FileIndex == 0 for NTFS complete?
I am testing against Windows2016 with a share on NTFS and it returns
FileIndex==0 also.
Can you check and clarify?
regards
ronnie sahlberg
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-12-03 3:07 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-12-03 3:07 FileIndex in FSCC FileIdFullDirectoryInformation ronnie sahlberg
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).