4.1.7 Slow To Respond To SMB Network Discovery...

Hello,

I got exactly the same problem with my Duo after ugrade to 4.1.7


greetings Berkhout

I've noticed similar behavior on a couple of NV+ units as well on both Win XP & Win 7 clients. Opening up My Computer for the first time with drives mapped to the NAS can take anywhere from 20-30+ seconds.

-Randy

I also have noticed slower response. Please note that I had 60 minute spin down timers set before the upgrade to 4.1.7 and continue to have those timers in place.
I have drive letters mapped on my vista box. On 4.1.6 when clicking on a network drive letter it was almost immediate, regardless of the spin down timers. Now on 4.1.7 I can wait up to 20 seconds before the contents of the drive are displayed and available to use. Definately something in the 4.1.7 upgrade that is doing this...

Hi,

Can one of the Jedis please let us know if this problem is being investigated and how far the investigation has advanced? It would also be helpful if we can have an indication of how long it will take for this to be fixed.

With my DUO holding lots of material for my media players I will need to revert firmware if this isn't fixed quickly. (I would welcome advice of any issues reverting from 4.1.7 production back to 4.1.6 production.)

By the way, where can we get the 4.1.6 production version of the firmware? It doesn't appear to be available on the ReadyNAS website.

Regards,
Ian.

I have the same issue. Performance was fine before the 4.1.7 upgrade and now the enumeration is so slow, I cannot mount any filesystems via cifsfs from a Linux box because it times out. Windows is able to perform the mounts, but the initial enumeration is appallingly slow. I'd rather not have to downgrade to 4.1.6, but this problem may force me to do so :(

For the record, with is an NV with 1GB of memory and 4 1.5GB Seagate drives.

I think I have the same problem - after upgrading my nv+ to 4.1.7, my macintosh clients (using cifs/smb) see the server and allow me to browse to the top couple of directories on it, but as soon as I try to list a directory that has a lot of files (several hundred) or perform actions that access multiple files, the mac times out and kills the smb connection. Here's what I see in the system log file on the mac:

Dec 3 08:16:50 myhostname KernelEventAgent[36]: tid 00000000 type 'smbfs', mounted on '/Volumes/mysharename', from '//GUEST:@myreadynasname%20(CIFS)._smb._tcp.local/mysharename', dead

[mysharename, myhostname and myreadynasname are not the real names of course]

When I try to re-install 4.1.7 by using using "check for update, I get an error saying "error connecting to remote server".
I am ok reverting to 4.1.6, but can't find a .bin file for it. The 4.1.6 I can download from :
http://www.readynas.com/download/RAIDiator/RAIDiator-4.1.6 is not a valid image (when I try and do a local update).

note: i also have the ftp service enabled, and it seems to work ok (albeit slowly).

Any help to resolve this soon would be greatly appreciated,
Thanks,
Jeremy

Me to.
Directory listing from mac to nas ultra are real slow.
Any guru able to help?

IanSav wrote:

Hi, Since upgrading my DUO to 4.1.7 I have noticed that the DUO is *very* slow to respond SMB/SAMBA network share enumeration requests. It may take up to about a minute for the DUO to provide its list of shares. The problem happens *every* time the DUO is asked to list its shares and not just for the first request. This was not an issue under 4.1.6. (I never ran any of the betas and upgraded from 4.1.6 production directly to 4.1.7 production. There were no obvious issues with the upgrade.)

I do have exactly the same problem - and I'm glad to read that I'm not the only one.
So, it's for very sure an issue with the upgrade.

I would appreciate if this bug would be fixed, soon.
(Would be a nice Xmas present ... - I hope that someone got the hint)

Hi,

It seems there are a few of us observing this issue (and taken the time to post). I think a comment from Netgear is appropriate.

Regards,
Ian.

IanSav wrote:
It seems there are a few of us observing this issue (and taken the time to post). I think a comment from Netgear is appropriate.

Yes, the least that they can do (instantaneously) is to publish how to downgrade to 4.1.6 - the last working version.
But I would prefer the bug to be fixed, of course.
4.1.7 has brought some improvements (the most important one for me: more silence - thanks to reduced fan speed after the disk spin-down).