[RFC PATCH] smbd: resilient file handle support

[Bryan Burgin]

Uri,

An update, following up on your comment "I [Uri] will check. I [Uri] have reports that we fail Windows 10 backup too unless downgrading to SMB2.0.2, but I haven't studied it closely as with Win8":

Regarding the Bugzilla report at https://bugzilla.samba.org/show_bug.cgi?id=10159 and the fix we created for Windows 8 via the on-demand (you have to pull down the fix) QFE patch https://support.microsoft.com/en-us/kb/2920193 and Windows 8.1 via the "important" Windows Update roll-up patch https://support.microsoft.com/en-us/kb/2919355 is also included in Windows 10.

The end-user scenarios that were reported back in 2013 was that the feature Windows Server Backup did not work when the target SMB2 server was a dialect 2.1 and above and, as was discovered as the root-cause, the server did not support FSCTL_LMR_REQUEST_RESILIENCY.  Samba servers at the time returned STATUS_NOT_SUPPORTED.  An API that Windows Server Backup relied on, CreateVirtualDisk(), did not consider FSCTL_LMR_REQUEST_RESILIENCY as an optional feature when the dialect was 2.1 or greater.  If the request for resiliency was not supported, the API failed and so did the feature.  The fix was to continue to request if FSCTL_LMR_REQUEST_RESILIENCY is supported (when the negotiated dialect is 2.1 or greater), but NOT to consider a response of STATUS_NOT_SUPPORTED as a hard failure.  This also affected other callers of CreateVirtualDisk(), which included using the Hyper-V Manager to create a new hard disk on a remote share.

I tested both Windows Server Backup on a Windows Server 2016 TP4 box and creating a VHDX from a Windows 10 box using the Hyper-V Manager against a server I modified to always return STATUS_NOT_SUPPORTED to FSCTL_LMR_REQUEST_RESILIENCY requests.  I am satisfied that the issue that was reported in 2013 and fixed soon thereafter continues to be fixed in Windows 10 and Server 2016.

If you have reports of issues, we would be very interested if additional information becomes available.  But, if there is a failure, it is likely a different root-cause that would need to be investigated.

Bryan

-----Original Message-----
From: Uri Simchoni [mailto:uri at samba.org] 
Sent: Tuesday, February 16, 2016 11:05 AM
To: Bryan Burgin <bburgin at microsoft.com>; samba-technical at lists.samba.org
Subject: Re: [RFC PATCH] smbd: resilient file handle support

On 02/16/2016 08:27 PM, Bryan Burgin wrote:
> Responding to: 
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2flists
> .samba.org%2farchive%2fsamba-technical%2f2016-February%2f112112.html&d
> ata=01%7c01%7cbburgin%40microsoft.com%7cab0f74b5dde44f54ca8c08d337041a
> a1%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=Wv8enCrIp9emtlr73s6T0X
> JQZ%2fWmmbRGimwOfJl5qlE%3d
>
> And 
> https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fbugzi
> lla.samba.org%2fshow_bug.cgi%3fid%3d10159&data=01%7c01%7cbburgin%40mic
> rosoft.com%7cab0f74b5dde44f54ca8c08d337041aa1%7c72f988bf86f141af91ab2d
> 7cd011db47%7c1&sdata=7yCAshPJHIz6uXjp5Fndo8juTs2Cx6tB0K2fb5kUwKs%3d
>
>
>
>
>
> Focusing on "Regarding "I didn't plan this. The driver for doing this was that we've just found out that Windows backup engine doesn't work with Samba and SMB dialect > 2.0.2 (see https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fbugzilla.samba.org%2fshow_bug.cgi%3fid%3d10159&data=01%7c01%7cbburgin%40microsoft.com%7cab0f74b5dde44f54ca8c08d337041aa1%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=7yCAshPJHIz6uXjp5Fndo8juTs2Cx6tB0K2fb5kUwKs%3d)", this was resolved several years ago when it was reported.  I'm with the Microsoft protocol support team and work with your Samba colleagues regularly on technical issues.  Please take note of KB 2920193: https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fsupport.microsoft.com%2fen-us%2fkb%2f2920193%3a&data=01%7c01%7cbburgin%40microsoft.com%7cab0f74b5dde44f54ca8c08d337041aa1%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=sZu50spM7WQE7tfVOqHEGl9Rqv7l8NYB%2bHpuLDHO4D8%3d "Virtual hard disk cannot be created on an SMB server without resiliency support from a Windows computer".  For Windows 8 and Server 2012, you need to download and install the patch.  For Windows 8.1 and Server 2012 R2, it was fixed automatically as long as the system installed the update rollup 2919355: https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fsupport.microsoft.com%2fen-us%2fkb%2f2919355.&data=01%7c01%7cbburgin%40microsoft.com%7cab0f74b5dde44f54ca8c08d337041aa1%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=zeZoFTxxOf3cN9QjVh8MOz5UzmvLrEQexHNlBITdevE%3d  This was fixed in Windows 10 before it was released, so there is no action necessary regarding Windows 10."
>
Bryan,

I will check. I have reports that we fail Windows 10 backup too unless downgrading to SMB2.0.2, but I haven't studied it closely as with Win8.

Thanks,
Uri.