All,

 

I am happily running version 4.4.2 (getting support for nfs was schweet!), but there is one little problem that pops up about once a week.  I have an NFS share mounted on three different Linux media servers (one mythtv backend/frontend combo and two frontends), and about once a week I get a stale NFS file handle.  When it goes stale, it happens on all three media servers.  None of the servers has been rebooted, the unraid system has not been stopped, and my network devices are all on UPS (as are the servers).  Uptime on all the boxes indicates there has been no reboot.  I did run a parity check on the unraid system.  Not sure if that would do it.

 

Other than that, I can't think of any reason for the mount to go stale.  Ideas?

I'm running 4.5 beta 6 and am also getting Stale nfs handle errors ... frequently.

 

My unraid server is connected to a gigabit hard wired network. I access my exported shares via a wired ubuntu box, and a Macbook Pro running Snow Leopard.

 

I'm currently copying files to my ubuntu box. While trying to copy files from my "Movies" share I'll often get a stale nfs file handle error. Yet if I acknowledge the error and cancel the transfer, mouse over to the file in question and double click it, the file is recognized and launches in my media player.  I can close the application and try copying the file again and it seems to copy fine.  It's the intermittent nature of these errors that is so frustrating. It's not an issue of any box going down, nothing has been rebooted. I initially thought that because I'm copying 2 or 3 mkv's at a time via a user share, maybe movie 2 or 3 was on a drive that had spun down while movie 1 was copying, but according to the unraid web interface all drives are spun up.  Any idea's, tweaks, etc?

I'm getting the same problem with stale NFS handles.

It happens randomly (seems random to me). Am considering using samba share to see if this problem goes away.

 

I am running UnRaid 4.5 beta 6

Not to pile on, but I'm having the same problems. UnRAID NAS (v4.5b6), NFS exports to MythTV Backend in /mnt/Media/xxxxx (4 separate shares) and is attached to MythTV using Storage Groups.

 

Just started getting ready for a rollout of 1 MythTV Frontend/Master and 4 Frontend/Secondary systems, but I hit this. I'm going to test the lastest UnRAID beta and then test 4.4.2 to see if I can reproduce. It happened relatively quickly for me (a couple hours, 3 at most) after idle, so hopefully I can go through a testing iteration every few hours. I'm wondering if it has to do with drive spin-down, but the share really should persist through that.

 

Worst case, I'll go to Samba.

Using unRAID 4.5.3 I'm getting hit by this bug a lot on one Ubuntu client and thus since I enabled user shares. When using NFS disk mounts rather than NFS user share I don't get the bug at all. I've switched to cifs mount until this get fixed.