Project

General

Profile

Feature #11017

Support Apple FULL_SYNC feature

Added by Gordon Ross 8 days ago. Updated 3 days ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Start date:
2019-05-15
Due date:
% Done:

0%

Estimated time:
Difficulty:
Medium
Tags:
needs-triage

Description

Something that came up at the last plug-fest. Apple clients don't trust servers to actually sync data to persistent storage unless we advertise the FULL_SYNC volume attribute in the Apple extension that queries volume properties.

The most obvious way to test this is to attempt to set up Apple "Time Machine" with our server as storage. The setup refuses to use the server unless it has both SMB2 leases and advertises the FULL_SYNC volume property.

Unfortunately, setting up Time Machine is complicated, requiring a functional (Multicast Domain Name Service) MDNS service with registrations for the SMB server and share to be found by Time Machine using MDNS. I tried briefly setting that up and ran out of time trying to get it the MDNS parts work so that Time Machine would find the share.

As an alternative verification method, we can connect using SMB2 from a Mac client and take a network trace. In the volume capabilities part of the SMB2 create response, AAPL create context element, we should see the FULL_SYNC flag when "drilling down" to that level with Wireshark.

History

#1

Updated by Gordon Ross 3 days ago

  • Status changed from New to In Progress
  • Description updated (diff)

Tested per the description.
Fix in production since late 2017

Also available in: Atom PDF