[cifs-protocol] [REG:116022313745563] Windows 10 backup failing against Samba
bburgin at microsoft.com
Wed Feb 24 20:09:38 UTC 2016
[casemail to bcc]
Is it possible that your code is having a problem seeing a [MS-RSVD] 126.96.36.199 SVHDX_OPEN_DEVICE_CONTEXT Structure with a version of two? There are now two RSVD Open Device context structures:
[MS-RSVD] 188.8.131.52 SVHDX_OPEN_DEVICE_CONTEXT, where Version must be RSVD_ECP_CONTEXT_VERSION_1 (0x00000001)
[MS-RSVD] 184.108.40.206 SVHDX_OPEN_DEVICE_CONTEXT_V2 Structure, where Version must be RSVD_ECP_CONTEXT_VERSION_2 (0x00000002)
In your trace, what was sent was a [MS-RSVD] 220.127.116.11 SVHDX_OPEN_DEVICE_CONTEXT_V2 Structure (first DWORD = 0x00000002).
As the root cause was resolved on this end, I closed the case, but if additional follow-up is required on our end I will be happy to open a new issue.
From: Uri Simchoni [mailto:uri at samba.org]
Sent: Wednesday, February 24, 2016 11:22 AM
To: Jeremy Allison <jra at samba.org>
Cc: Bryan Burgin <bburgin at microsoft.com>; cifs-protocol at lists.samba.org; MSSolve Case Email <casemail at microsoft.com>
Subject: Re: [cifs-protocol] [REG:116022313745563] Windows 10 backup failing against Samba
On 02/24/2016 09:17 PM, Jeremy Allison wrote:
> Yep, just found it. Sorry for the noise :-).
> Strange place to return NT_STATUS_INVALID_DEVICE_REQUEST but there you
> go.... :-).
It's probably based on the idea that SVHDX is implemented by the backing store, the (apparently-incorrect-on-this-point) spec says that if the data store doesn't support SVHDX, this error is to be returned, which lead us to get this create context to the VFS and generate the error from there.
But probably this error should not be generated.
More information about the cifs-protocol