I upgraded from 4.4 to 4.5 beta 13.  I noticed an immediately slow down when trying to page through a user share (hit page down, wait 15 seconds until next list of folders shows up) ...  After a few weeks of this I figured I'd need to downgrade.  I found that when I went to get old versions of the software from the download page, none were available but there was a 4.5 final version available.  I was hoping this would solve my problem so I upgraded.

 

I use the UNRAID server to store a large quantity of media files I torrent.  I use uTorrent 1.8.4 but since this was working for 2.5 years I figure the change in uTorrent is the problem here.  So what happens is after an arbitrary amount of time, all the torrents fail with the message "The specified network location is no longer available".  At that time if I try to use windows explorer to navigate to my unraid server, none of the user shares will be available.  I am still able to connect to the webpage on tower and it looks normal.

 

So I guess my question is 'what happened'?  Should I downgrade the server again?  Intermittently having all my in progress downloads stop is a major pain.

What happens when you try 4.5 FINAL? I think they changed the asynchronous i/o option in the final, which may have been causing you issues earlier.

 

Are you also running the "cache_dirs" user addon script?

 

4.5 Final is when the network began dissappearing. 

 

I am running the cache_dirs user addon but it seems to me that when I started using that, I started getting the slow browsing of user shares.  To test it,  removed it and saw no improvement to that problem, so I put it back in.  I installed that add on at the same time I installed 4.5 beta 13 so I assumed beta 13 caused the issue which is why I was considering downgrading.  I had no problems with the older version, I'm not sure why I upgraded.

Please see the Troubleshooting link in my sig, and capture and post your syslog.  The syslog logs most of your server activity, especially errors.  It may be useful to capture a syslog from both a version that seems to work well and from a version where it is failing, so we can compare.