Shadowcopy volume block devices

Corinna Vinschen
Sun Jun 2 08:56:00 GMT 2013

On Jun  1 19:46, Micky wrote:
> > I'm looking forward to your feedback.
> This is now working like a charm! On the upside, I noticed one more
> thing. Unlike dd on traditional cmd, your implementation doesn't copy
> the zero blocks -- which to its considerable benefit is a humongous
> time saver for me as now I don't have to compress the image to save
> space! Whether this was intentional or not, I think we should keep it
> this way. And I do appreciate your instant fix!

Thanks, but my "implementation" just opens the device and reads from
it.  There's no other magic involved.  If it doesn't copy zero blocks,
it's an OS feature.

> > Btw., as a sidenote, are you aware that you can access the filesystem
> > underneath the volume shadow copy as well?
> Yea, that was the first thing I noticed. I thought it was cool since I
> don't have to run diskshadow.exe or mklink to mount a volume. Just
> open up the bash and everything is there for you. Whoever came up with
> this idea, is a fathomable genius :)!
> Btw, when is this going to be released in stable branch? I did test
> the dumped image by restoring it, which also worked fine.

I intend to release 1.7.19 at the start of this week, probably Monday
or Thursday.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list