2.1.2.1 Reparse Tags
Each reparse point has a reparse tag. The reparse tag uniquely identifies the owner of that reparse point. The owner is the implementer of the file system filter driver associated with a reparse tag.
Reparse tags are exposed to clients for third-party applications. Those applications can set, get, and process reparse tags as needed. Third parties MUST request a reserved reparse tag value to ensure that conflicting tag values do not occur. [WHDC-RPTR]<1>
The following reparse tags, with the exception of IO_REPARSE_TAG_SYMLINK, are processed on the server and are not processed by a client after transmission over the wire. Clients should treat associated reparse data as opaque data.<2>
|
Value |
Meaning |
|
IO_REPARSE_TAG_RESERVED_ZERO 0x00000000 |
Reserved reparse tag value. |
|
IO_REPARSE_TAG_RESERVED_ONE 0x00000001 |
Reserved reparse tag value. |
|
IO_REPARSE_TAG_MOUNT_POINT 0xA0000003 |
Used for mount point support, specified in section 2.1.2.5. |
|
IO_REPARSE_TAG_HSM 0xC0000004 |
Obsolete. Used by legacy Hierarchical Storage Manager Product. |
|
IO_REPARSE_TAG_HSM2 0x80000006 |
Obsolete. Used by legacy Hierarchical Storage Manager Product. |
|
IO_REPARSE_TAG_DRIVER_EXTENDER 0x80000005 |
Home server drive extender.<3> |
|
IO_REPARSE_TAG_SIS 0x80000007 |
Used by single-instance storage (SIS) filter driver. Server-side interpretation only, not meaningful over the wire. |
|
IO_REPARSE_TAG_DFS 0x8000000A |
Used by the DFS filter. The DFS is described in the Distributed File System (DFS): Referral Protocol Specification [MS-DFSC]. Server-side interpretation only, not meaningful over the wire. |
|
IO_REPARSE_TAG_DFSR 0x80000012 |
Used by the DFS filter. The DFS is described in [MS-DFSC]. Server-side interpretation only, not meaningful over the wire. |
|
IO_REPARSE_TAG_FILTER_MANAGER 0x8000000B |
Used by filter manager test harness.<4> |
|
IO_REPARSE_TAG_SYMLINK 0xA000000C |
Used for symbolic link support. See section 2.1.2.4. |
