ReadyNas PRO6 hangs when BulkCopy

There Was a RAID-Fault and a C:Resync one or two days before I took the log
But that is very seldom

I had not to reboot from a hang
I had never to reboot from a hang
the hang disappears after 30...60Seconds waiting

The NAS ist OFF by default. I only boot it when some data from the NAS is needed

The NAS works perfect now (50% DiskLoad). 85% Load was too mutch for the NAS

Bernhard

Okay. When it is hanged up, can you access FrontView or other services besides CIFS? Trying to narrow down if network interface issue, or Samba/CIFS alone.

chirpa wrote:
Okay. When it is hanged up, can you access FrontView or other services besides CIFS? Trying to narrow down if network interface issue, or Samba/CIFS alone.

Yes - you are right
I can access FreontView at that time when the Samba Access is blocked
Samba is also blocked for other computers at that time (30...60Seconds)
when that Time is over the whole bulk copy will work without any other block
it's only one time - never many times - for one bulk-copy
it only appears with large amount of data is copied to the NAS (VM-Ware machine - Directory of RAW-Files from my EOS 1Ds3 - or something like that )
it never appears when ony reading or copying small files to the NAS

Bernhard

The smbd.log in your System Log zip does not have enough history in it to get an idea of possible errors. Best thing I can suggest is next time it happens, get the logs right away.

chirpa wrote:
The smbd.log in your System Log zip does not have enough history in it to get an idea of possible errors. Best thing I can suggest is next time it happens, get the logs right away.

Have reproduced the Hang on my Backup-machine that is still quite full
Something leads to broken pipes
see the SMBD-log snipset below
On my main NAS the problem is gone since I have the diskload down to 50%

thank you

Bernhard

[2013/05/30 10:13:25,  0] smbd/server.c:1143(main)
  smbd version 3.5.21 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2010
[2013/05/30 10:19:13.362992,  2] auth/auth.c:314(check_ntlm_password)
  check_ntlm_password:  Authentication for user [Bernhard] -> [Bernhard] FAILED with error NT_STATUS_NO_SUCH_USER
[2013/05/30 11:10:49.524984,  2] auth/auth.c:314(check_ntlm_password)
  check_ntlm_password:  Authentication for user [Bernhard] -> [Bernhard] FAILED with error NT_STATUS_NO_SUCH_USER
[2013/05/30 11:12:43.558067,  0] lib/util_sock.c:680(write_data)
[2013/05/30 11:12:43.558189,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2013/05/30 11:12:43.558232,  0] smbd/process.c:79(srv_send_smb)
  Error writing 51 bytes to client. -1. (Transport endpoint is not connected)
[2013/05/30 11:12:43.558438,  0] lib/util_sock.c:680(write_data)
[2013/05/30 11:12:43.558472,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/05/30 11:12:43.558514,  0] smbd/process.c:79(srv_send_smb)
  Error writing 104 bytes to client. -1. (Transport endpoint is not connected)
[2013/05/30 11:12:43.558806,  0] lib/util_sock.c:680(write_data)
[2013/05/30 11:12:43.558862,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/05/30 11:12:43.558894,  0] smbd/process.c:79(srv_send_smb)
  Error writing 51 bytes to client. -1. (Transport endpoint is not connected)
[2013/05/30 11:12:43.559112,  0] lib/util_sock.c:680(write_data)
[2013/05/30 11:12:43.559156,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/05/30 11:12:43.559188,  0] smbd/process.c:79(srv_send_smb)
  Error writing 51 bytes to client. -1. (Transport endpoint is not connected)
[2013/05/30 11:12:43.559360,  0] lib/util_sock.c:680(write_data)
[2013/05/30 11:12:43.559394,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/05/30 11:12:43.559424,  0] smbd/process.c:79(srv_send_smb)
  Error writing 51 bytes to client. -1. (Transport endpoint is not connected)
[2013/05/30 11:12:43.559553,  0] lib/util_sock.c:680(write_data)
[2013/05/30 11:12:43.559586,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/05/30 11:12:43.559630,  0] smbd/process.c:79(srv_send_smb)
  Error writing 51 bytes to client. -1. (Transport endpoint is not connected)
[2013/05/30 11:12:43.559780,  0] lib/util_sock.c:680(write_data)
[2013/05/30 11:12:43.559810,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/05/30 11:12:43.559839,  0] smbd/process.c:79(srv_send_smb)
  Error writing 51 bytes to client. -1. (Transport endpoint is not connected)
[2013/05/30 11:12:43.560000,  0] lib/util_sock.c:680(write_data)
[2013/05/30 11:12:43.560046,  0] lib/util_sock.c:1441(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
  write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/05/30 11:12:43.560123,  0] smbd/process.c:79(srv_send_smb)
  Error writing 51 bytes to client. -1. (Transport endpoint is not connected)

http://www.bernhard-hartl.com/Share/System_log-NAS2-20130530-111304.zip

getting the same issue, did this topic ever get resolved?

currently running 4.2.23 on a Pro6

ephect wrote:
getting the same issue, did this topic ever get resolved? currently running 4.2.23 on a Pro6

NO - it was NOT RESOLVED
I have got 4.2.23 on Pro6 - two systems
have added some larger disks for more free space on both NAS Systems
The Bug is still there but it only appears when the free diskspace is low

Bernhard

bugger.. thanks for the reply though.

i would love to say that could fix it, but we only have 700gb used of a possible 5.4tb.

Strictly to do with Samba / CIFS per your messages. I've stumbled on this earlier myself and do notice that the IP it's trying to get to is 0.0.0.0 which could indicate a downed NIC. Hence why a restart probably worked for me (having documented this)

The same issue documented here:

http://microdevsys.com/wp/error-writing-bytes-to-client-transport-endpoint-is-not-connected/

Then with Samba / CIFS look into some of the issues here for debugging tips and scanning on your network:

http://microdevsys.com/wp/networking-sharing-folders-between-windows-and-linux-using-samba/3/

I remember running into this when the NIC card chip was broken (82574L) and couldn't handle the traffic. Try a search on the above pages for that as well. Hopefully this moves you along further.

Regards,