I think problem we are having is this exact problem in samba mailing lists. http://lists.samba.org/archive/samba/2007-July/133789.html seems that it's problem with samba 3.0.25b

 

Bugzilla is here https://bugzilla.samba.org/show_bug.cgi?id=4796

The official bug report...  made to the samba developers is here:

https://bugzilla.samba.org/show_bug.cgi?id=4796

 

and their patch to fix the problem is here:

https://bugzilla.samba.org/attachment.cgi?id=2827

 

Tom... looks like you might just have an answer for your next release.

 

Joe L.

Can't wait for a beta with this patch on it, having to do some serious planning to get data onto the unRAID box when it will not error out

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.

The version of smbd that has the disconnect bug is 3.0.25b

 

To tell if you have the buggy version, login via telnet and type:

/usr/sbin/smbd -V

 

The working version is 3.0.24.

I sure the buggy version of smbd is in unRaid 4.2 and think it might even be in 4.1. Edit: unRaid 4.1 uses version 3.0.24 of smbd.

 

I've now got a copy of smbd 3.0.24 on my flash drive.  I've also added a line to my "go" script to copy

it to /usr/sbin/smbd just prior to emhttp being invoked.

This will fix the disconnect bug for me until Tom can get a newer version in a new release of unRaid.

cp /boot/smbd /usr/sbin/smbd; chmod +x /usr/sbin/smbd

 

Joe L.

PS.

easiest way to get the older version is to boot up an older release of unRaid and then copy the file to the flash drive.

cp /usr/sbin/smbd /boot/smbd

Then, boot up the newer release and the file should be there for your use.  I got my older (version) copy of smbd from unRaid 4.0beta9 since I had it on my alternate flash drive.

That doesn't work. But thanks for the idea Here is edited version.

 

I'm running 4.2 beta 3 here is what I did.

 

To use \\tower\flash share you need to enable it from the web interface first.

 

Copied bzimage, bzboot and syslinux.cfg from 4.1 zip to flash share and rebooted. When 4.1 was running did "cp /usr/sbin/smbd /boot" from commandline

 

Then edited go file on flash share to look like this

 

#!/bin/bash

 

# Shutdown Samba then copy samba 3.0.24 to sbin and start samba

killall smbd nmbd

sleep 2

cp /boot/smbd /usr/sbin/smbd

chmod +x /usr/sbin/smbd

/etc/rc.d/rc.samba

 

# Start the Management Utility

/usr/local/sbin/emhttp &

 

Then copied bzimage, bzboot and syslinux.cfg from 4.2 beta3 zip to flash share and rebooted.

 

That's it.

Is it just me or does sambe 3.0.24 work better? It use to choke on listing directories especially when you copies something to unRAID server while browsing directories.

I did not realize that smbd would have already been started in the "rc" scripts... I thought it was started by emhttp.  Oops... no harm, just the copy would not have occurred since the file was in use.

 

Thanks for the update to really make it work.

FYI: A slightly modified copy of the samba "rc" script exists at /root.

 

You could have done exactly the same thing with

 

/root/samba stop

sleep 3

cp /boot/smbd /usr/sbin/smbd

chmod +x /usr/sbin/smbd

/root/samba start

 

# Start the Management Utility

/usr/local/sbin/emhttp &

 

What version of smbd did you find on the 4.1 version of unRaid?  Is it the 3.0.24 version? Edit: it is the 3.0.24 version.

 

 

edit: added "sleep 3" to my script to allow time for smbd to quit when stopped.

Joe L.

Is it just me or does sambe 3.0.24 work better? It use to choke on listing directories especially when you copies something to unRAID server while browsing directories.

Choking on long directory listings while writing to the server sounds like exactly the same bug, just the symptoms when file explorer ran into it.  (It seemed to show itself when reading while writing)

 

Joe L.

4.1 has samba 3.0.24

And thanks for making my go script look better

Your script modification doesn't work. Seems that after stopping samba you need to wait a while so samba process is really killed.

 

Like this

 

/root/samba stop

sleep 2

 

But i thought probably using killall with -w switch would be best to make sure samba process has been killed when copy happens so i modified go script to look like this.

 

#!/bin/bash

 

# Overwrite samba 3.0.25b with samba 3.0.24

killall -w smbd nmbd

cp /boot/smbd /usr/sbin/smbd

chmod +x /usr/sbin/smbd

/root/samba start

 

# Start the Management Utility

/usr/local/sbin/emhttp &

 

You were right. My copy failed, and I was still using the buggy version of "smbd"

 

Either of your solutions will work.  I just added a "sleep 3" command and it worked just fine. 

 

I expect that Tom will replace the buggy version of smbd with a working version in the next release, so this is a temporary band-aid.

 

Thanks for being a very cooperative "tester"

 

Joe L.

Can someone post the working smbd here so we don't all have to go back to an earlier version, extract it, go back to the current, replace it?

 

Thanks!

Can someone post the working smbd here so we don't all have to go back to an earlier version, extract it, go back to the current, replace it?

 

Thanks!

 

The working version of smbd is over 3 meg in size.  The attachment limit on this board is 100k. 

 

If I did it right, the 3.0.24 version of smbd should be downloadable at this link: http://www.mediafire.com/?3ym2dgnydys

 

Joe L.

Brilliant work people ! Im so glad I started this thread.

 

Anyway since we know have discovered, debugged and found a fix for the problem I think it is reasonable to ask for an ETA on the next beta (since this one is essentially dead due to this bug).

 

Nice one

DL'd just fine. I'll try it tonight. Thanks Joe!

If you want to install the latest 3.0.26a version of smbd, you can download it from this link: http://www.mediafire.com/?2hgen2d1xso

 

That link is to a zip file containing smbd version 3.0.26a  (in a usr/sbin/ sub-folder) and also a WHATSNEW.txt document (in a usr/docs sub-folder), describing the change history.

 

There have been many changes since version 3.0.24.  They did fix the problem with the disconnects we were seeing, a few "memory leaks", a security issue or two along with lots of other items so I figured I'd give it a try.  I downloaded it as part of a huge 26 meg  binary distribution from the Slackware site (Unraid is based on Slackware).

 

I am currently using the 3.0.26a version of smbd on my unRaid server, copying it into place while samba is stopped as described earlier in this thread in the "go" script. 

 

smbd 3.0.26a is working just fine and is not disconnecting from windows the way 3.0.25b did.

 

Joe L.

Weird. I have "Version 3.0.25b" and i copied 500gb onto unRAID yesterday without incident.  Just to kick the tires i went ahead and in compressed a 4gb rar to an unRAID user share while it was going and it didn't worked fine.

 

I was having some odd stability problems with unRAID over the weekend but i tweaked my setttings a bit and underclocked my memory timings by a notch and it seems very stable now.

ok, one more question before I hit this tonight. Does the copy have to be done EVERYTIME the system is booted via the go script, or does it stay once put in? I'm assuming everytime you reboot, as the smdb is copied from the flash each time.

someone smarter could correct me if i'm wrong but i belive that the deal here is that the whole linux distrobution is in a single archive file so that we monkeys dont break it so in order to use a different somba version you have to wait for it to boot, shut down the one from the archive and load your new version directly into memory.  So yeah, i think that it has to happen everytime.

ok, one more question before I hit this tonight. Does the copy have to be done EVERYTIME the system is booted via the go script, or does it stay once put in? I'm assuming everytime you reboot, as the smdb is copied from the flash each time.

You are correct, The copy to "/usr/sbin" has to be done every time the system is re-booted.  That is because every time you reboot the "/usr/sbin" directory is created in RAM, and is initially populated with the version of smbd that is contained in the "bzroot" file.  (bzroot is a form of a compressed archive, somewhat similar to a zip file)

 

When unRaid is booted, the bzroot file is "unzipped" into the in-memory filesystem.  That puts the buggy version of smbd into place in /usr/sbin/smbd.  As part of its start-up, unRaid also starts "smbd" running.

 

When the "go" script executes, the extra lines we added stops the"smbd" process, copies the newer "smbd" file from the flash drive to /usr/sbin/smbd, and then re-starts "smbd"  (as part of samba)

 

Joe L.

Tested 3.0.26a and it's working without any problems.

Brilliant work people ! Im so glad I started this thread.

 

Agreed!  As you probably know, 4.2 was released today without this fix; however, I'll produce a 4.2.1 release A.S.A.P. that includes Samba 3.0.26a.

I loaded 4.2.1 this morning and the performed three tasks that had a high probability of producing the error...cloning a DVD directly to a user share with Clone DVD, and compiling two DVD's directly to a user share with TMPGEnc DVD Author.  All three finished successfully after installing 4.2.1.

 

I wouldn't call it conclusive as the error rate was never 100% for these things, but three consecutive successful events in the first three tries seems like a pretty good indication that 4.2.1 may have rectified this problem.

 

 

I am seeing this issue with 4.5 beta 6.

When copying files I get the same error:

 

The specified network name is not longer available

 

My memory in unraid is completely gone and as soon as I cancel the error dialog it returns.

 

 

Sometimes copying one large file it will go through but not release the memory.

I will attach a screen shot.