Windows System Software -- Consulting, Training, Development -- Unique Expertise, Guaranteed Results

Sept/Oct 2019 Issue of The NT Insider available

Download PDF here:

It’s a particularly BIG issue, too: 40 pages of technical goodness, ranging from WDF to Minifilters. Check it out.
Before Posting...
Please check out the Community Guidelines in the Announcements and Administration Category.

How volsnap driver know this write operation should be copy-on-write or not?

Sooncheol_WonSooncheol_Won Member Posts: 19
edited October 28 in NTDEV

I'm studying Volume Shadow Copy Service.

In Windows Internals Part 2,

Volsnap avoids copy-on-write operations for the paging file, hibernation file, and the difference data stored in the System Volume Information folder. All other files will get copy-on-write protection.

Volsnap driver is upper volume filter driver so I think it cannot figure out this writing block(sector) is from what filename or what file attributes has but it maybe can.

How can volsnap know that information?

And how does volsnap know which logical block is not used and how does volsnap redirect to where writing operations? (to another block? or to temporary file?)


  • Sooncheol_WonSooncheol_Won Member Posts: 19

    I found some variable in IRP structure.


    This looks like contains original file object which has filename, attributes and Vpb...
    Does volsnap uses these and redirect to some other backup file?

Sign In or Register to comment.

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Upcoming OSR Seminars
Writing WDF Drivers 21 Oct 2019 OSR Seminar Space & ONLINE
Internals & Software Drivers 18 Nov 2019 Dulles, VA
Kernel Debugging 30 Mar 2020 OSR Seminar Space
Developing Minifilters 27 Apr 2020 OSR Seminar Space & ONLINE