2.4.38 FileReparsePointInformation
This information class is used locally to query for information on a reparse point.
A FILE_REPARSE_POINT_INFORMATION data element, defined as follows, is returned to the caller.
|
|
|
|
|
|
|
|
|
|
1 |
|
|
|
|
|
|
|
|
|
2 |
|
|
|
|
|
|
|
|
|
3 |
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
FileReferenceNumber |
|||||||||||||||||||||||||||||||
|
... |
|||||||||||||||||||||||||||||||
|
Tag |
|||||||||||||||||||||||||||||||
FileReferenceNumber (8 bytes): The 64-bit file ID, as specified in section 2.1.9, for the file.
Tag (4 bytes): A 32-bit unsigned integer value containing the reparse point tag that uniquely identifies the owner of the reparse point. Section 2.1.2.1 contains more details on reparse tags.
This operation returns a status code as specified in section 2.2. Upon success, the status code returned by the function that processes this file information class is STATUS_SUCCESS. The most common error codes are listed in the following table.
|
Error code |
Meaning |
|---|---|
|
STATUS_INFO_LENGTH_MISMATCH 0xC0000004 |
The specified information record length does not match the length that is required for the specified information class. |
|
STATUS_INVALID_DEVICE_REQUEST 0xC0000010 |
The target file system does not implement this functionality. |
|
STATUS_INVALID_INFO_CLASS 0xC0000003 |
The specified information class is not a valid information class for the specified object. |
|
STATUS_NO_SUCH_FILE 0xC000000F |
No reparse points exist for the given file. |
|
STATUS_BUFFER_OVERFLOW 0x80000005 |
The output buffer was filled before all of the FILE_REPARSE_POINT_INFORMATION structures could be returned; a partial structure might be returned. |