jj666 Posted August 20, 2011 Share Posted August 20, 2011 Seem to be having some strange issues with Beta 11 re: NFS shares. All three of my UNRaid servers are linked via NFS mounts in the first server share directory, like so: mount -t nfs 192.168.1.58:/mnt/user/Share /mnt/user/Share/unraid2 mount -t nfs 192.168.1.44:/mnt/user/Share /mnt/user/Share/unraid3 So that YAMJ can process all of the three server movie files together. Previously with 4.7, whenever I changed anything on server 2, or server 3, I unmounted the NFS shares, and remounted, which worked perfectly well. I noticed some strange errors (Stale NFS File Handles) today in the YAMJ output and looking at the third server via Windows, it seemed to have access denied errors, when trying to enter NFS mount/movies/art, or NFS mount/movies/nfo directories. Looking at the syslog for the machine where the mounts are located, I see the following errors, repeated multiple times. Aug 20 14:22:04 Tower kernel: NFS: server 192.168.1.58 error: fileid changed Aug 20 14:22:04 Tower kernel: fsid 0:e: expected fileid 0xb00000f5, got 0xffffffffb00000f5 Aug 20 14:23:19 Tower kernel: NFS: server 192.168.1.44 error: fileid changed Aug 20 14:23:19 Tower kernel: fsid 0:f: expected fileid 0xa0000006, got 0xffffffffa0000006 etc etc Is that something I need to set up different with v5.0, or a bug? Note all three machines are running 5.0 B11. Cheers, -jj- Quote Link to comment
jj666 Posted August 20, 2011 Author Share Posted August 20, 2011 Rolling back both mounted servers to Beta 9 seems to have fixed the issues (same problem with Beta 10). Cheers, -jj- Quote Link to comment
crazytony Posted August 26, 2011 Share Posted August 26, 2011 I'm experiencing this as well on b11. There is zippo in the syslog or dmesg on the unraid box. The interesting thing is that it's only doing it to files on a relatively new disk. Old files/folders on other disks do not show the same symptom. Quote Link to comment
mav3r1ck Posted August 29, 2011 Share Posted August 29, 2011 Running unRAID Beta 12 with Slackware 13.37: Aug 29 12:53:41 Goliath mountd[10613]: Kernel does not have pseudo root support. Aug 29 12:53:41 Goliath mountd[10613]: NFS v4 mounts will be disabled unless fsid=0 Aug 29 12:53:41 Goliath mountd[10613]: is specfied in /etc/exports file. Aug 29 12:57:28 Goliath mountd[10614]: Caught signal 15, un-registering and exiting. Aug 29 12:57:32 Goliath rpc.nfsd[10724]: error starting threads: errno 38 (Function not implemented) I don't seem to be able to start the NFS server. Any idea? thanks! I think I already found out why I didn't had the NFS server support flagged in the kernel.. rebuilding now. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.