NAS

Cannot copy ... : The specified network name is not longer available

53 posts in this topic

Getting the message "Cannot copy ... : The specified network name is not longer available" quite a bit with the beta.

 

Specifically when copy data to User folders (is that the corect term to describe the concatenated multi disk multi folder thing?)

 

usually if i persevere i can get the data up (just by trying again).

 

No syslog messages are ever created.

 

Any ideas?

0

Share this post


Link to post
Share on other sites

I've seen the exact same thing happen to me a couple times since upgrading to 4.2.  I've actually had it happen both when writing to user shares and insividual disks.  I can also confirm that nothing ever registers in the log.  It seems network connectivity is only broken for a second (just long enought to interrupt the file transfer) since I can browse the user share/disk immediately after I see the error mesage pop up.

0

Share this post


Link to post
Share on other sites

i got this a couple of times in 4.1, turns out my server ran out of memory and needed a reboot

0

Share this post


Link to post
Share on other sites

i got this a couple of times in 4.1, turns out my server ran out of memory and needed a reboot

How did you know the server ran out of memory?

0

Share this post


Link to post
Share on other sites

I've had this happen with some frequency as well. Three times today actually. I'll start to author a DVD (using TMPGEnc DVD Author) and have it write the files directly to a user share. It'll crap out part way through with the error noted above. But if I compile the dvd to a local drive, then I can copy completed folder over to unraid with no problem.

0

Share this post


Link to post
Share on other sites

i got this a couple of times in 4.1, turns out my server ran out of memory and needed a reboot

How did you know the server ran out of memory?

 

logged into the console, typed 'top' and Mem had 0k free, after about 2 minutes, the movie i was playing stopped playing, and the box pretty much became unresponsive

 

turned it off & on, and that seemed to fix the issue

0

Share this post


Link to post
Share on other sites

limetech what can we do to assist debug this problem. Since syslog is empty what else can we check for you?

0

Share this post


Link to post
Share on other sites

I too had intermittent disconnects, usually when playing a movie while writing to the unRaid array.  A re-try re-connected.

 

This thread might have the solution: http://lime-technology.com/forum/index.php?topic=1027.msg6938#msg6938

 

I applied the nolapic directive and re-booted about 1 1/2 hours ago.  So far, no disconnects.

 

 

Edit: It was not the answer... it did not do any harm, but disconnects continued.

0

Share this post


Link to post
Share on other sites

limetech what can we do to assist debug this problem. Since syslog is empty what else can we check for you?

 

Hey NAS User,

 

Could you try something and copy a few GIGs of files to see if it helps any?

 

I had the exact same issue when I was running 4.0 and 4.1 and fixed after adding a line in syslinux

 

When I Upgraded to 4.2.4b, a new syslinux copies over the one I modified so I added the nolapic back in and I am not having any network lost issues at all for all 4.x versions.

 

Here's what my syslinux looks like... could you add the nolapic in yours, reboot and copy a few Gigs of files to see if it helps?

 

This is from version 4.2.4b

default menu.c32
menu title Lime Technology LLC
prompt 0
timeout 50
label unRAID OS
  menu default
  kernel bzimage
  append initrd=bzroot rootdelay=10 nolapic
label Memtest86+
  kernel memtest

 

The line Append includes nolapic at the end

  append initrd=bzroot rootdelay=10 nolapic

 

 

0

Share this post


Link to post
Share on other sites

let me try my new intel card in a couple of days and if it reoccurs i will start trying the apci stuff.

 

FYI it just happened again copying to a user share. Tried 5 times didn't work then i copyed to the real on disk location and it worked flawlessly.

0

Share this post


Link to post
Share on other sites

Intel card is a no go. So i am on to syslinux kernel codes

 

Question: where can i find documentation on "nolapic" as all the docs i can find say this should be "noapic" << notice the missing "l"

0

Share this post


Link to post
Share on other sites

I too had intermittent disconnects, usually when playing a movie while writing to the unRaid array.  A re-try re-connected.

 

This thread might have the solution: http://lime-technology.com/forum/index.php?topic=1027.msg6938#msg6938

 

I applied the nolapic directive and re-booted about 1 1/2 hours ago.  So far, no disconnects.

Today, while using bittorrent, it got to a point where the samba share would disconnect if I attempted to play a video on the SAME pc as was writing to the unRaid server.    Looks like the nolapic directive had no effect. (or not the complete solution)

 

I also had a telnet window open to the unRaid server displaying the "top" command.  I was not out of memory (6928k free) and the telnet session did not disconnect when the samba share momentarily disconnected. (was not available for writing by bittorrent)

 

When the disconnect occurred, the movie I was playing also froze, so it looks like samba just froze momentarily. It also looked like the network itself still had connectivity. (telnet session showed no errors)

 

No entry in the syslog at all when these errors occur.  I looked there first for a clue.

 

Looks like it is time to turn on debugging in the samba server.

 

Joe L.

0

Share this post


Link to post
Share on other sites

I killed the smbd process and then ran smbd with -d3  option from the command line in a telnet window and tried once more.  I captured a failure.  I tried again with debug level 10, so far, no failure... figures... :'(

 

Joe L.

 

I got this when the error occurred with level 3 debug enabled:

Lots of logged message flew by in the telnet window... what follows is the tail end of the message when the samba disconnect occurred.
<snip...>
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
call_trans2qfilepathinfo: TRANSACT2_QFILEINFO: level = 258
call_trans2qfilepathinfo data/New Folder (3)/abcd/abcd.rar (fnum = 9811) level=258 call=7 total_data=0
Transaction 1358 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1359 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1360 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1361 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1362 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=8192 nread=8255
Transaction 1363 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1364 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1365 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1366 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1367 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=8192 nread=8255
Transaction 1368 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1369 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1370 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1371 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1372 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=8192 nread=8255
Transaction 1373 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1374 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1375 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1376 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1377 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=8192 nread=8255
Transaction 1378 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1379 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1380 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1381 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1382 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=8192 nread=8255
Transaction 1383 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1384 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1385 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1386 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1387 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=8192 nread=8255
Transaction 1388 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1389 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1390 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1391 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1392 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=8192 nread=8255
Transaction 1393 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1394 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1395 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1396 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1397 of length 76
switch message SMBtrans2 (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
call_trans2qfilepathinfo: TRANSACT2_QFILEINFO: level = 1005
call_trans2qfilepathinfo data/New Folder (3)/xyzzy.avi
(fnum = 9798) level=1005 call=7 total_data=0
Transaction 1398 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=8192 nread=8255
Transaction 1399 of length 69
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=1 wrote=1
Transaction 1400 of length 84
switch message SMBtrans2 (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
call_trans2qfilepathinfo: TRANSACT2_QFILEINFO: level = 258
call_trans2qfilepathinfo data/New Folder (3)/abcd/abcd.rar (fnum = 9811) level=258 call=7 total_data=0
Transaction 1401 of length 16452
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9798 num=16384 wrote=16384
Transaction 1402 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1403 of length 16452
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9798 num=16384 wrote=16384
Transaction 1404 of length 88
switch message SMBnttrans (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
call_nt_transact_notify_change
call_nt_transact_notify_change: notify change called on data/New Folder (3), fil
ter = FILE_NAME|DIR_NAME, recursive = 1
Transaction 1405 of length 65604
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9811 num=65536 wrote=65536
Transaction 1406 of length 16452
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9798 num=16384 wrote=16384
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
Transaction 1407 of length 88
switch message SMBnttrans (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
call_nt_transact_notify_change
call_nt_transact_notify_change: notify change called on data/New Folder (3), fil
ter = FILE_NAME|DIR_NAME, recursive = 1
Transaction 1408 of length 63
switch message SMBreadX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
fcntl_getlock: fd 28 is returned info 2 pid 0
send_file_readX: sendfile fnum=9807 max=61440 nread=61503
Transaction 1409 of length 16452
switch message SMBwriteX (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
writeX fnum=9798 num=16384 wrote=16384
Transaction 1410 of length 88
switch message SMBnttrans (pid 2979) conn 0x803f17f8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
call_nt_transact_notify_change
call_nt_transact_notify_change: notify change called on data/New Folder (3), fil
ter = FILE_NAME|DIR_NAME, recursive = 1
read_data: read failure for 4 bytes to client 192.168.2.6. Error = Connection reset by peer
timeout_processing: receive_smb error (Connection reset by peer) Exiting
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
vfs_ChDir to /mnt/disk8
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
dellcpx (192.168.2.6) closed connection to service disk8
Yielding connection to disk8
vfs_ChDir to /
setting sec ctx (0, 0) - sec_ctx_stack_ndx = 0
vfs_ChDir to /mnt/disk3
root closed file data/New Folder (3)/abcd/abcd.rar (numopen=5) NT_STATUS_OK
root closed file data/New Folder (3)/abcd.rar (numopen=4
) NT_STATUS_OK
error packet at smbd/notify.c(114) cmd=160 (SMBnttrans) NT_STATUS_OK
write_data: write failure in writing to client 192.168.2.6. Error Broken pipe
Error writing 75 bytes to client. -1. (Broken pipe)
root@Tower:/boot#

root@Tower:~# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:11:11:75:FB:7E
          inet addr:192.168.2.3  Babcd:192.168.2.255  Mask:255.255.255.0
          UP BROADabcd NOTRAILERS RUNNING MULTIabcd  MTU:1500  Metric:1
          RX packets:18878599 errors:0 dropped:0 overruns:0 frame:0
          TX packets:26230056 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:1432440944 (1.3 GiB)  TX bytes:1317406627 (1.2 GiB)
          Base address:0x9c00 Memory:ff800000-ff820000

0

Share this post


Link to post
Share on other sites

I'll add a "me too" to this issue on both of my machines running 4.2b4 using the original intel mobo.

0

Share this post


Link to post
Share on other sites

just as an fyi i can find no pattern in the way a user access unRAID to setting this of. All i can say is copying more than one file to a user share seems to set it off more often that an other action.

0

Share this post


Link to post
Share on other sites

I tried again with debug level on smbd set to 10.

 

No further detail was given.

 

as before, he last two debug lines preceding the crash were:

read_data: read failure for 4 bytes to client 192.168.2.6. Error = Connection reset by peer

timeout_processing: receive_smb error (Connection reset by peer) Exiting

 

It happens whenever I try to play a movie stored on the unRaid server WHILE I am using bittorrent to download files TO a /mnt/disk3/data folder on the unRaid server from the same PC.  I was not reading, nor writing to the user-shares at the time the error occurred. 

 

It is repeatable if reading/playing a movie and writing from bittorrent from the SAME PC.  Within a few minutes of starting the movie, the errors occur.

 

So far, it does not seem to occur when I am playing a movie on one of my MG-35 lan-based media players from a file on the unRaid array, even though I am writing to to it from the PC from a running bittorrent.

 

Joe L.

 

 

 

Joe L.

0

Share this post


Link to post
Share on other sites

Trying to reproduce this - so far have not, though I have not tried writing with any bittorrent program.

 

Joe, can you try again, this time reading movie direct from a disk share, not a user share, if possible?

0

Share this post


Link to post
Share on other sites

Tom,

 

I was not using any "User Share" at all in my tests.  Sorry if I did not make that more clear in my previous post.

 

I was downloading a bittorrent using Azureus as the client to \\tower\disk3\data\new folder(3)\file...

I was playing a different movie file from \\tower\disk3\data\new folder(3)\other_file

 

My disk shares are read/write, but hidden. I have to type the path to get to the files, they do not show in windows explorer

 

So... I do not think the user-shares have anything to do with it.

 

The bittorrent's can run for hours unless I try to play a movie using the same PC.  Then the connection breaks, apparently with some kind of timeout.

 

Joe L.

0

Share this post


Link to post
Share on other sites

I've run into this as well, thought I chalked it up to being a beta release.  I was using user-shares however, but had similar results, the main difference was that I was seeding the torrents so the client was only reading data...any other activity on the disk that lasted more then a few seconds would cause the torrents to error out seeding until I rechecked them.

0

Share this post


Link to post
Share on other sites

This happened me yesterday when i was copying 40GB to user share. I'm running 4.2 beta 3 with P5B-VM DO, Intel Core 2 Duo E4400, 2x 512MB kingston 533mhz ddr2. I have 4 500GB drives + 1 500GB parity drive. No memory errors. Tested with memtest 86+ and windiag with multiple passes.

It had copied around 30GB over and was copying one allmost 2GB file and after that file i got this error. I was moving files to user share.

 

Odd thing is that this little less than 2GB file was copied but wasn't delete from my machine that i was moving this file from.

Sadly i didn't check if that file was ok on unraid server but overwrote it in my stupidity.

Share i'm moving files to was like //tower/myusershare. So it wasn't mapped drive if that has anything to do with it.

 

Since i have Core 2 Duo so it should do multiprocessing maybe this is might some dual processor problem? Maybe code isn't thread safe?

 

Let me know how can i check my logs to see if there is something there.

 

Also i might have been seeding some files of unRaid with bittorrent during this error or not. I have couple of files in my seeding que that are on unRaid server so depending if they where started or not during that copy.

0

Share this post


Link to post
Share on other sites

thought it might be worth mentioning that i never torrent to unRAID and i still see this error

0

Share this post


Link to post
Share on other sites

thought it might be worth mentioning that i never torrent to unRAID and i still see this error

I think the error has something to do with simultaneous reading and writing.  Bittorrent happens to do a lot of that, so it will encounter the error more frequently than other programs.

 

Yesterday, I saw the network disconnect error occur when the bittorrent program was NOT in use.

 

Joe L.

0

Share this post


Link to post
Share on other sites

I was seeing this error with 4.2.4b but having gone back to 4.1 it has disappeared. I too was only writing, not streaming at the same time.

0

Share this post


Link to post
Share on other sites

I was seeing this error with 4.2.4b but having gone back to 4.1 it has disappeared. I too was only writing, not streaming at the same time.

Yes, but even when "*we*" think we are only writing, windows itself is often doing "reads" to keep itself in sync for folder listings, etc.

 

I don't think I ever saw it in 4.1 either.  Probably should try older version of smbd and see if problem goes away. (It could be samba, it could be the networking itself, it  could be in the OS.  Need to start isolating the cause one thing at a time)

 

Joe L.

0

Share this post


Link to post
Share on other sites

Copyright © 2005-2017 Lime Technology, Inc. unRAID® is a registered trademark of Lime Technology, Inc.