lacie 5 big network v.1 please support for fvdw

[taetae]

ok and how can I retrieve the log to post it here??


update :


retrieving the file log.smdb in var\ log\ samba

Code: Select all

[2014/02/22 12:45:37, 0] smbd/server.c:main(942)
  smbd version 3.0.37 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2014/02/22 13:14:22, 0] smbd/nttrans.c:call_nt_transact_ioctl(2463)
  call_nt_transact_ioctl(0x1401c4): Currently not implemented.
[2014/02/22 13:15:44, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.29. Error = Connection reset by peer
[2014/02/22 13:15:44, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.29. Error Broken pipe
[2014/02/22 13:15:44, 0] lib/util_sock.c:send_smb(761)
  Error writing 75 bytes to client. -1. (Broken pipe)

another attempt

Code: Select all

[2014/02/22 12:45:37, 0] smbd/server.c:main(942)
  smbd version 3.0.37 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2014/02/22 13:14:22, 0] smbd/nttrans.c:call_nt_transact_ioctl(2463)
  call_nt_transact_ioctl(0x1401c4): Currently not implemented.
[2014/02/22 13:15:44, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.29. Error = Connection reset by peer
[2014/02/22 13:15:44, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.29. Error Broken pipe
[2014/02/22 13:15:44, 0] lib/util_sock.c:send_smb(761)
  Error writing 75 bytes to client. -1. (Broken pipe)
[2014/02/22 13:31:58, 0] smbd/nttrans.c:call_nt_transact_ioctl(2463)
  call_nt_transact_ioctl(0x1401c4): Currently not implemented.
[2014/02/22 13:36:44, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.29. Error = Connection reset by peer
[2014/02/22 13:36:44, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.29. Error Broken pipe
[2014/02/22 13:36:44, 0] lib/util_sock.c:send_smb(761)
  Error writing 75 bytes to client. -1. (Broken pipe)

[Jocko]

Well,...

Your output is a standard output : you don't change the debug level... and its content says only that at 13:15:44, you closed the samba connection (stop your PC and standby it).

So what you should do:
- change the debug level like I wrote in the previous post.
- try to copy a big file from your NAS on your PC
- and read the log files when the writing failed

[taetae]

in putty I gave the following commands

Code: Select all

/rw_fs/tmp/var/log/samba # killall smbd
/rw_fs/tmp/var/log/samba # /usr/sbin/smbd -D -l /var/log/samba -d 1
/rw_fs/tmp/var/log/samba #


log :

Code: Select all

[2014/02/22 12:45:37, 0] smbd/server.c:main(942)
  smbd version 3.0.37 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2014/02/22 13:14:22, 0] smbd/nttrans.c:call_nt_transact_ioctl(2463)
  call_nt_transact_ioctl(0x1401c4): Currently not implemented.
[2014/02/22 13:15:44, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.29. Error = Connection reset by peer
[2014/02/22 13:15:44, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.29. Error Broken pipe
[2014/02/22 13:15:44, 0] lib/util_sock.c:send_smb(761)
  Error writing 75 bytes to client. -1. (Broken pipe)
[2014/02/22 13:31:58, 0] smbd/nttrans.c:call_nt_transact_ioctl(2463)
  call_nt_transact_ioctl(0x1401c4): Currently not implemented.
[2014/02/22 13:36:44, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.29. Error = Connection reset by peer
[2014/02/22 13:36:44, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.29. Error Broken pipe
[2014/02/22 13:36:44, 0] lib/util_sock.c:send_smb(761)
  Error writing 75 bytes to client. -1. (Broken pipe)
[2014/02/22 13:54:27, 0] smbd/server.c:main(942)
  smbd version 3.0.37 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2014/02/22 13:55:21, 1] smbd/service.c:make_connection_snum(1042)
  carmine (192.168.1.29) connect to service Venere initially as user carmine (uid=1000, gid=1000) (pid 1289)
[2014/02/22 13:55:54, 0] smbd/nttrans.c:call_nt_transact_ioctl(2463)
  call_nt_transact_ioctl(0x1401c4): Currently not implemented.
[2014/02/22 13:57:08, 0] smbd/reply.c:send_file_readX(2614)
  send_file_readX: sendfile failed for file Sistemi operativi/Office 2013/Office 2013 64bit/Office_64.iso (Broken pipe). Terminating
[2014/02/22 13:57:08, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.29. Error Broken pipe
[2014/02/22 13:57:08, 0] lib/util_sock.c:send_smb(761)
  Error writing 75 bytes to client. -1. (Broken pipe)
[2014/02/22 13:57:10, 1] smbd/service.c:make_connection_snum(1042)
  carmine (192.168.1.29) connect to service Venere initially as user carmine (uid=1000, gid=1000) (pid 1291)

[Jocko]

So the log allows to finfd what is wrong :

Code: Select all

[2014/02/22 13:57:08, 0] smbd/reply.c:send_file_readX(2614)
  send_file_readX: sendfile failed for file Sistemi operativi/Office 2013/Office 2013 64bit/Office_64.iso (Broken pipe). Terminating

It seems to be a known issue with a google search I found this :http://forums.nas4free.org/viewtopic.php?f=21&t=1702

This evening, I will study more this issue.

[taetae]

ok ... I continue to test all

but I can guarantee that it does also on file from 20 mb 15 mb ....

[Jocko]

I found nothing conclusive unless you use a non-standard mtu value.

So on your PC and I assume that you use a windows OS.
open a command window and do

Code: Select all

netsh interface ipv4 show subinterfaces

you can get the mtu value for each NIC (should be 1500)

[fvdw]

:dontknow I juts copied a 5 GB file form my nwsp2 to pc running windows and it completed fine without interuption, avarage speed was around 30 MB/s

Does this happen for any big file ? or just this perticular one. (it could be hanging on a bad block on the disk, but hen you would expect the same problem with ftp protocol, so not likely)

This must be a LAN problem. I assume you using windows 7 , so you could view ween the task manager the network traffic when transferring the file to see how stable the transfer is. If it varies a lot between zero and max speed then something is interfering the communication

[taetae]

mtu: 1500 windows 7 sp1

I changed the network before rising all the cables I have is cat 6 and cat 5e



the problem with them as well with large files and small files but only via network resources

travels through ftp beissimo ....

the network is composed of an 8-port gigabit swicth where they are connected to the PC and a router

if I try to do steps of small and large files between PCs on the network everything is great

if I try to Nas or nos to the pc I have problems ... I also noticed that sometimes hangs just flipping through the contents of Nas

The pc I'm doing tests that sits at home has been formatted, and then I do not think is a problem of communication or clogging ..... Then I point out that it does on all PC's in my possession


I attach the picture to let you know what happens ....

[taetae]

To clarify even better I did another test where you start a file of 100 MB and fortunately it ends and then one from 300mb but then that leaves unexpectedly crashes and repeating the same operation does not change the result.


the different colors is to distinguish the files

blue 100mb, 300mb red, yellow second test 300mb

[taetae]

no news :dontknow :dontknow ? in two days I get home so I'll be physically close to Nas