Re: server-side-copy: seems not to get used

Am 24.03.26 um 15:24 schrieb Rowland Penny via samba:

> I have no idea, my share is on an ext4 filesystem using Samba 4.22.6
> and I connected from Samba 4.23.5

that's exactly my setup

>> I am comparing 2 shares now: the home of root is located on an
>> internal RAID array while other shares are on a LUN on a SAN.
> 
> That could be part of the problem, I am connecting to a filesystem, you
> appear to be connecting to a mount, so even though you are connecting
> to a 'share', that share is actually a mount of a storage device that is
> elsewhere, it all adds latency. It might also affect server-side copy,
> who knows ?

Yep. That's why I tested 2 shares:

- one on the HPE-MSA storage
- one on a local disk in the samba-server

Makes no real difference.

I re-read the report from the user there:

he wrote he sees 60 MB/s in LAN
and 2 MB/s over VPN

I can't tell so far if his client enables/asks for SSC, maybe tmrw I can 
test that when he's at home.

I also CC-ed their windows- and vpn-admin. Maybe some AV-scanner slows 
down things (mis-trusting the remote LAN when on VPN or so).
> The thing is, you are trying scopy and the file is being copied, but,
> from what you have said, there is no sign of it being copied to the
> client running smbclient and then back to the server under a new name,
> this to me would suggest server-side copy is being used, just not as
> fast as you would like.

maybe, yes

I set up wireshark for remote ssh dump, and traced another test with 
smbclient. SSC seems to work, but some google-result told me:

"If you are analyzing slow file transfers, a server-side copy should be 
fast. If it is slow, analyze the SMB2 response times (Statistics -> 
Service Response Times -> SMB2) to check for high latency in the IOCTL 
commands. "

Did that:

  cat Downloads/smb2_stats.txt
===========================================================================
SMB2 Service Response Time Statistics - SSH remote capture: sshdump:
Index  Procedure  Calls  Min SRT (s)  Max SRT (s)  Avg SRT (s)  Sum SRT (s)
---------------------------------------------------------------------------
SMB2
Negotiate Protocol          0      1     0.013087     0.013087 
0.013087     0.013087
Session Setup          1      2     0.001048     0.004653     0.002850 
   0.005701
Tree Connect          3      6     0.000911     0.014472     0.003674 
  0.022043
Tree Disconnect          4      3     0.000330     0.000610     0.000436 
     0.001309
Create          5     36     0.000379     0.258409     0.011528     0.414997
Close          6     35     0.000108     0.000680     0.000261     0.009132
Read           8      2     0.012179     0.019644     0.015911     0.031823
Write          9    256     0.000230     0.001829     0.000766     0.196060
Ioctl         11    900     0.000235     0.982685     0.048411    43.570254
Find          14     21     0.000054     0.258409     0.018917     0.397261
Notify         15      4     5.691715    21.549351    13.620769    54.483078
GetInfo         16     65     0.000146     0.001421     0.000562 
0.036550
SetInfo         17      3     0.000050     0.000388     0.000193 
0.000579
---------------------------------------------------------------------------


I don't really know if that's OK or bad, it's just visible that Ioctl 
and Notify are rather high.

I will continue analyzing this tomorrow.

thanks so far




-- 
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba