Very slow copy with SMB

[Geeks_Alex]

Hello,

I have very slow copy with SMB since 6.9.0 : 9 Mo/s. Normaly it's 90-100 Mo/s

Tested without SM3 Encryption. It's the same.

Anyone can't help me. Someone have the same problem. Can y reinstall SMB ?

Thanks

[Geeks_Alex · Accepted solution]

Just to say the encryption on SMB3 is to difficult for ARM on RN102 and that why SMB use all the CPU ressource with very slow copy.

[Geeks_Alex]

I have very hight CPU on the NAS : 90%

[Kardano]

I can confirm that.

All my backup jobs which took data from or to windows share are EXTREME SLOW.

on FW 6.8.1:

Backup Job Name: UT Backup
Backup Job Type: Incremental
Protocol: cifs
Backup Source: [remote:cifs]///192.168.77.100/uTorrent
Backup Destination: [Backup]/uTorrent
Backup Start Time: Fri Oct 20 2017  0:05:08
Backup Finish Time: Fri Oct 20 2017  0:05:09
Backup Status: Success


Copy File  resume.dat
Copy File  resume.dat.old
Copy File  settings.dat
Copy File  settings.dat.old

On FW 6.9.0 that job is running for hours a still does not complete.

Client or source of shares are 2 diferrent Windows 7 PC's.

There is no high CPU usage on NAS.

There is someting terribly wrong with FW 6.9.0

tried this:

Disable Opplocks -  no change

Disable SMB Encrypt - no change

[mdgm-ntgr]

What are the full settings for the backup job? What kind of SMB backup is it?

Moved this thread. The Beta section is strictly for questions about beta firmware.

[Kardano]

full settings for backup job:

Windows/NAS (Timestamp) -> share

Source:

Type: remote - Windows/NAS (Timestamp)

host: defined as IP

path: share On PC

(test connection is OK)

Destination:

share on NAS

Schedule

every 24 hours 0:05-0:05

Options

scheduke full backup: first time

On completion send: status and errors

Remove selected contents of backup destination before backup - NOT selected

After backup is complete, change ownership of files.... - NOT selected

last log entry for this job: when was complete, FW 6.8.1

Backup Job Name: UT Backup
Backup Job Type: Incremental
Protocol: cifs
Backup Source: [remote:cifs]///192.168.77.100/uTorrent
Backup Destination: [Backup]/uTorrent
Backup Start Time: Fri Oct 20 2017  0:05:08
Backup Finish Time: Fri Oct 20 2017  0:05:09
Backup Status: Success


Copy File  resume.dat
Copy File  resume.dat.old
Copy File  settings.dat
Copy File  settings.dat.old

Now is job showing status: In Progress

running for about 5 hrs.....

same thing happening (not wokring) for jobs which are:

share -> remote: Windows/NAS (Timestamp)

last log entry for this type of job: when was complete, FW 6.8.1

Backup Job Name: Documents_Personal_Cajo7n
Backup Job Type: Incremental
Protocol: cifs
Backup Source: [Documents]/Personal
Backup Destination: [remote:cifs]///192.168.77.2/Documents/personal
Backup Start Time: Thu Oct 19 2017 22:05:07
Backup Finish Time: Thu Oct 19 2017 22:05:09
Backup Status: Success


Copy File  Rozpočet 2017.xlsx
Copy File  Vydaje 2017.xlsx
Copy File  Vydaje Porovnanie.xlsx

All Rsync jobs are OK.

are these setting sufficient for you?

NAS is RN204.

 All SMB jobs was OK until updating FW from 6.8.1 to 6.9.0.

After updating nFW to 6.9.0 no SMB/cifs job was completed. 1st described job was running for 20 hrs but not completed. After cancellation of jpb (i hoped, tat is some kind of error and it block another jobs) noting is writed on jobs log.

[mdgm-ntgr]

Geeks_Alex have you checked what's using up lots of CPU on your NAS?

[Geeks_Alex]

Hello,

Thanks to your reply.

Yes Samba it self (smbd)

[Geeks_Alex · Accepted solution]

Just to say the encryption on SMB3 is to difficult for ARM on RN102 and that why SMB use all the CPU ressource with very slow copy.

[Kardano]

for me it does not help. I turned off SMB3 encryption. Client PC is Windows 7 Pro x64.

I make new backup Job. Files in job are copied OK. but then job is In progress forever and does not stop. It happens on my RN104 and RN204. Tried from 2 different windows 7 PC. the same.

[StephenB]

Can you measure the speed with NAStester?  http://www.808.dk/?code-csharp-nas-performance

[Kardano]

May i ask what is your client OS?

Thanks

[Kardano]

For RN204

NAS performance tester 1.7 http://www.808.dk/?nastester
Running warmup...
Running a 400MB file write on \\PMNAS02\transfer 5 times...
Iteration 1:     74,60 MB/sec
Iteration 2:     78,40 MB/sec
Iteration 3:     77,56 MB/sec
Iteration 4:     73,14 MB/sec
Iteration 5:     74,15 MB/sec
-----------------------------
Average (W):     75,57 MB/sec
-----------------------------
Running a 400MB file read on \\PMNAS02\transfer 5 times...
Iteration 1:     96,34 MB/sec
Iteration 2:     92,82 MB/sec
Iteration 3:     91,00 MB/sec
Iteration 4:     95,56 MB/sec
Iteration 5:     99,26 MB/sec
-----------------------------
Average (R):     94,99 MB/sec
-----------------------------

For RN104:

Running a 400MB file write on \\PMNAS01\transfer 5 times...
Iteration 1:     31,36 MB/sec
Iteration 2:     32,98 MB/sec
Iteration 3:     33,64 MB/sec
Iteration 4:     33,72 MB/sec
Iteration 5:     32,22 MB/sec
-----------------------------
Average (W):     32,79 MB/sec
-----------------------------
Running a 400MB file read on \\PMNAS01\transfer 5 times...
Iteration 1:     57,58 MB/sec
Iteration 2:     58,93 MB/sec
Iteration 3:     57,70 MB/sec
Iteration 4:     57,93 MB/sec
Iteration 5:     56,61 MB/sec
-----------------------------
Average (R):     57,75 MB/sec
-----------------------------

i tried restart outh NAS units, router, switches... nothing help.

No difference if client PC is Windows 7 or Windows 10.

Files are copied, jobs hangs at "In progres"...

[StephenB]

So it looks like the RN204 speeds have dropped about 10 MB/sec over what you reported here: https://community.netgear.com/t5/New-to-ReadyNAS/Transfer-speed-on-rn204/m-p/1027539/highlight/true#... I wouldn't call that "very slow", but it is a noticable drop.

Do you know what the RN104 was giving you before?

Also, has anything changed on your network since your earlier report?

>>>May i ask what is your client OS?

My PCs are all Windows-10 now.  My windows application server and my RN52x NAS use 10gbaseT, which is of course a lot faster than gigabit.

[Kardano]

[Kardano]

I installed FW 6.8.1 to my RN204 (RN104 is FW 6.9.0 for test)

run SMB job and gues what? It works on TF 6.8.1:

Backup Job Name: UT Backup
Backup Job Type: Incremental
Protocol: cifs
Backup Source: [remote:cifs]///192.168.77.100/uTorrent
Backup Destination: [Backup]/uTorrent
Backup Start Time: Tue Oct 24 2017 20:43:54
Backup Finish Time: Tue Oct 24 2017 20:43:55
Backup Status: Success

 This is RN204 back on FW 6.8.1:

Running warmup...
Running a 400MB file write on \\pmnas02\transfer 5 times...
Iteration 1:     87,07 MB/sec
Iteration 2:     84,19 MB/sec
Iteration 3:     74,79 MB/sec
Iteration 4:     76,45 MB/sec
Iteration 5:     82,10 MB/sec
-----------------------------
Average (W):     80,92 MB/sec
-----------------------------
Running a 400MB file read on \\pmnas02\transfer 5 times...
Iteration 1:    110,92 MB/sec
Iteration 2:    102,80 MB/sec
Iteration 3:    112,35 MB/sec
Iteration 4:    112,48 MB/sec
Iteration 5:    105,31 MB/sec
-----------------------------
Average (R):    108,77 MB/sec
-----------------------------

[StephenB]

So your issue is just with the backup job, not with SMB generally?

[Kardano]

I think that it is something on FW 6.9.0. Because AFTER install FW 6.9.0 ALL SMB backup jobs does not end correctly. Old or new created. When i downgrade one unit to FW 6.8.1 all jobs on downgraded unit are OK.

Jobs on another unit (RN104 FW6.9.0) still hang after copy all files on status "in progres" and does not end at all. Jobs for rsync work OK on both units.

For me it seems that there is something in FW 6.9.0 causing problem.

It makes no difference if client PC is Windows 10, Windows 7, Windows 2003 server.

no difference if job is new created or old one from earlier FW.

Only think that makes difference is using FW 6.8.1 instead of FW 6.9.0.

RN104 and RN204 was configured independently. But on Both is problem after upgrade to FW 6.9.0. So i thing that is not some "problem on config" on both unit.

[StephenB]

---

@Kardano wrote:

I think that it is something on FW 6.9.0. Because AFTER install FW 6.9.0 ALL SMB backup jobs does not end correctly. Old or new created. When i downgrade one unit to FW 6.8.1 all jobs on downgraded unit are OK.

I was asking if you are seeing issues with SMB in 6.9.0 in normal use (that is, not in the backup jobs).

[Kardano]

No problems with SMB. Speed seems to be OK for both units.

Problem is with backup jobs using SMB only.

(i'm not sure what is oroblem in the job, because i tried to control speed of copy (by time) for jobs and it seem that fires are copied about thes same speeed on both FW 6.8.1 and 6.9.0. It seem that thjere is some problem in next phase in job (after copying files). I dont know how to call that. Som it may be that SMB protocol is OK, but job is doing something wrong?