NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
[4.1.9-T6] samba crash and general feedback
First, let me say a big THANK YOU for upgrading the Samba to a version that supports SMB2. Several friends and myself had all manually upgraded to Samba 3.6.1 (and then to 3.6.3) in order to make iTunes usable. TimeMachine now finally appears to work for my husband's MacOS Lion laptop as well. It's great to have a supported solution.
Unfortunately, after the upgrade I am having multiple problems:
-the shares are no longer browsable. start+run->"\\nas" results in a failure.
-from my win7 login, I can browse to "\\nas\matt" and see the directory listing, but on the same machine, switching users and trying to browse to \\nas\geoff does not work at all (trying with IP address doesn't help). the directories are still there under /c/, and re-running smbpasswd doesn't help.
-under \\matt\nas, it takes minutes to load a 1MB JPG. this used to be instantaneous.
I've double-checked and cleaned up the Samba 3.6.x install (based on the flumps.org instructions), and there doesn't appear to be any conflicts.
One of the reasons we chose Samba 3.6.x was that 3.5.11 did not appear to be stable using SMB2 with mixed Vista/Win7 clients over the course of a few weeks. Maybe a final bump to 3.5.13 will fix the issues we saw, but 3.6.x is the only version they say has reasonably complete SMB2 support.
So, I'll be jumping back to samba-3.6.3, which allowed my iTunes library to be hosted on a samba share and quickly sync my iPad/iPhone. With 3.6.3 and a few config tweaks, my iPhone/iPad sync times went from literal days (sometimes without completing) to hours. (I'm running iTunes 10.6 on win7/x64.)
I'm happy to provide logs, or even remote shell access to aid in debugging. Or, if you guys are in the bay area, I can bring in my ReadyNAS unit. This is a fixable problem, just a matter of figuring out how to get the installable image to get there :)
Thanks again!
PS: When can we expect a similar bump to the openssl0.9.8u package and to the OpenSSH 5.x package?
Unfortunately, after the upgrade I am having multiple problems:
-the shares are no longer browsable. start+run->"\\nas" results in a failure.
-from my win7 login, I can browse to "\\nas\matt" and see the directory listing, but on the same machine, switching users and trying to browse to \\nas\geoff does not work at all (trying with IP address doesn't help). the directories are still there under /c/, and re-running smbpasswd doesn't help.
-under \\matt\nas, it takes minutes to load a 1MB JPG. this used to be instantaneous.
I've double-checked and cleaned up the Samba 3.6.x install (based on the flumps.org instructions), and there doesn't appear to be any conflicts.
One of the reasons we chose Samba 3.6.x was that 3.5.11 did not appear to be stable using SMB2 with mixed Vista/Win7 clients over the course of a few weeks. Maybe a final bump to 3.5.13 will fix the issues we saw, but 3.6.x is the only version they say has reasonably complete SMB2 support.
So, I'll be jumping back to samba-3.6.3, which allowed my iTunes library to be hosted on a samba share and quickly sync my iPad/iPhone. With 3.6.3 and a few config tweaks, my iPhone/iPad sync times went from literal days (sometimes without completing) to hours. (I'm running iTunes 10.6 on win7/x64.)
I'm happy to provide logs, or even remote shell access to aid in debugging. Or, if you guys are in the bay area, I can bring in my ReadyNAS unit. This is a fixable problem, just a matter of figuring out how to get the installable image to get there :)
Thanks again!
PS: When can we expect a similar bump to the openssl0.9.8u package and to the OpenSSH 5.x package?
16 Replies
Replies have been turned off for this discussion
- If you're using the version that's included in the T-6 build, that's fine. It's not like I'm trying to argue. Let me put it this way. let's say Honda gives you a new car to test and wants to know how it works. But the first thing you do is swap the engine out, then tell them the car no longer starts. They can't do anything with that. Does it make sense now why we can't consider manually changing the samba version to something different as a beta issue?
Your feedback about the improved AFP support seems about as expected compared to other people(and it is appreciated), and we are aware of the issue some people have reported with AFP requiring a 2nd connection before working. matt_hargett wrote: After researching and experimenting for months with jumbo frames, socket options, and other things that made small differences, turning on SMB2 seemed to be the last thing that resolved my problem. That being said, when I then worked backward -- keeping SMB2 enabled while reverting other configuration changes -- the improvements were diminished. Here is an excerpt of the diff between the original smb.conf and the new one I was using:
So when you were using the Samba 3.5 from 4.1.9-T6, did you disable SMB2? You would also have to reboot the Windows client to stop using SMB2, because Windows tends to remember that we used to support it from its initial negotiation, and keeps using it -- and Samba will go along with it, even if max protocol is set to NT1.
Also, how many image files are in your test directory when it takes 10 minutes to display a single image? Is this over a wired or wireless connection?- Ah, that appeared to be the problem: I turned off smb2 then bounced samba and winbind, but didn't reboot the Win7 client machine. After a reboot, things are working *beautifully*. Thanks so much for your patience as I relayed my complicated story! :)
I'll keep testing over the next few days and let you know if I run into any issues. I am already noticing that with jumbo frames turned on and the aforementioned diffs, CPU still appears to be the bottleneck. Is there a source package for the samba version you guys are bundling? 'apt-get source samba' retrieves the stock Debian version, and adding a deb-src entry to the ReadyNAS package site doesn't work.
Will there be an OpenSSH/OpenSSL update in the next beta, as also provided on flumps.org? - I am seeing an intermittent crash, which gdb says is a double free. This may be one of the crash issues already fixed in 3.5.13:
http://www.samba.org/samba/history/samba-3.5.13.html matt_hargett wrote:
Is there a source package for the samba version you guys are bundling?
Once a production firmware is released the new samba would be put in the GPL: http://www.readynas.com/gpl- If you add
deb http://www.readynas.com/packages 4.1.9/
to /etc/apt/sources.list, you should be able to pull Samba 3.5.13 (until we post a new beta with it included).Will there be an OpenSSH/OpenSSL update in the next beta, as also provided on flumps.org?
I'll see if we can look into it.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
