shadow_copy2_realpath() snapshot path component removal
realrichardsharpe at gmail.com
Thu Feb 13 15:26:02 MST 2014
On Thu, Feb 13, 2014 at 2:21 PM, David Disseldorp <ddiss at suse.de> wrote:
> On February 13, 2014 11:00:37 PM CET, Richard Sharpe <realrichardsharpe at gmail.com> wrote:
>>One thing I notice in looking at the code is that it does not seem to
>>behave the way Windows really does.
>>For example, if your snapshots are read-only, I suspect that users
>>will get ACCESS_DENIED messages when trying to open a shadow-copy file
>>for write-like access, but Windows allows such access and returns
>>VOLUME_WRITE_PROTECTED when you try to actually perform write-like
> I expect that's just a side-effect of VSS doing the COW snapshot at the block layer.
> I.e. The filesystem/SD permit write access, but the IOs are rejected at the device layer.
Of course it is, but that is not the point. Users get very unhappy
when it does not behave the way it behaves on Windows.
More information about the samba-technical