Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

My computer just did a chkdisk, and when it finished processing file records, it said it had processed "44 reparse records". What exactly are they?

share|improve this question
1  
Tried to make sense of this --> pcguide.com/ref/hdd/file/ntfs/filesReparse-c.html but failed. Leaving it as a comment so that someone can decipher that and post as an answer, can make me understand better :) –  Sathya Apr 23 '10 at 23:05
    
So basically it's just another thing they're checking on your computer. It does not mean that it has actually fixed anything. –  user112741 Jan 8 '12 at 21:51

2 Answers 2

up vote 16 down vote accepted

Reparse Points are a feature of NTFS that provide a mechanism for file system filter drivers to intercept a file access request and potentially rewrite it. They provide the mechanism that powers several other NTFS features:

  • Volume mount points
  • Directory junctions
  • Symbolic links
  • Single Instance Storage
  • Native Structured Storage
  • Hierarchical Storage Management

Sathya's link provides a more in-depth look:

An application that wants to use the feature stores data specific to the application -- which can be any sort of data at all -- into a reparse point. The reparse point is tagged with an identifier specific to the application and stored with the file or directory. A special application-specific filter (a driver of sorts) is also associated with the reparse point tag type and made known to the file system. [...]

[...] When the file system goes to open the file, it notices the reparse point associated with the file. It then "reparses" the original request for the file, by finding the appropriate filter associated with the application that stored the reparse point, and passing the reparse point data to that filter. The filter can then use the data in the reparse point to do whatever is appropriate based on the reparse point functionality intended by the application.

The way the file system driver (FSD) figures out the file system filter (or mini filter) is by checking the ReparseTag of the meta-data and for third-party reparse points a GUID that is part of each reparse point's meta-data. The above list of features are mostly those supplied by Microsoft as part of various Windows versions and editions (junctions introduced in Windows 2000, symbolic links in Vista/2008), but one may request to be assigned a GUID by Microsoft as pointed out in MSDN here (comment section).

share|improve this answer

It allows windows to dynamically "attach" additional functions to its basic set of disk operations. Imagine the simple process of walking through a door--you normally turn the door knob, push the door open, pass through doorway and then close the door. What if you needed to check for packages at your front door, but only the front door. A reparse point would allow you to attach a "check for package" process that says whenever I pass through a door, first check for packages, then process walking through the door. The filter part allows you to specify when to apply the reparse, such as only at the front door should I check for packages.

share|improve this answer
    
This is only an analogy, not much of an explanation. It would've been better placed as a comment under the first answer. –  Jan Doggen Nov 8 '14 at 15:32
    
This is not an answer to the original question. To critique or request clarification from an author, leave a comment below their post - you can always comment on your own posts, and once you have sufficient reputation you will be able to comment on any post. –  DavidPostill Nov 8 '14 at 16:15

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.