unRAID Server Release 6.0-beta3-x86_64 Available


limetech

Recommended Posts

@SchoolBusDriver

is this necessary to add to syslinux.cfg as well ?

 

iommu=1

 

That isn't my call to make.

 

I am making suggestions to Tom from his point of view with everyone in mind.

 

I haven't tried running Xen with iommu=1 on a motherboard / bios that doesn't support / do IOMMU to see what happens (good, bad, nothing).

 

If I was Tom, I would leave it out. When someone wants to do PCI Passthrough they will follow a guide and have to add the PCI Device IDs to syslinux.cfg anyway. Adding iommu=1 at the same time shouldn't be an issue. Plus, I suspect that the people who do need / use PCI Passthrough will be small compared to those who do not.

Link to comment
  • Replies 661
  • Created
  • Last Reply

Top Posters In This Topic

will the new permission also set the permission on the usb key which holds the shares configuration?

 

I can see the following:

No, but flash is a vfat volume and what you see is normal and correct.

 

Ok I completed the new permission script, it completed successfully, but my shares are not back yet.

 

Anything else I can do?

 

 

root@Tower:/mnt# ls

cache/  disk11/  disk14/  disk17/  disk3/  disk6/  disk9/

disk1/  disk12/  disk15/  disk18/  disk4/  disk7/  user/

disk10/  disk13/  disk16/  disk2/  disk5/  disk8/  user0/

root@Tower:/mnt# cd user

root@Tower:/mnt/user# ls

movies/  series/

root@Tower:/mnt/user# cd series/

root@Tower:/mnt/user/series# ls

root@Tower:/mnt/user/series# cd ..

root@Tower:/mnt/user# cd ..

root@Tower:/mnt# ls -l

total 0

drwxrwxrwx  6 nobody users 136 Feb  7 17:25 cache/

drwxrwxrwx 12 nobody users 272 Jul 28  2011 disk1/

drwxrwxrwx  5 nobody users 104 Oct  6 17:37 disk10/

drwxrwxrwx  6 nobody users 128 Jul 15  2011 disk11/

drwxrwxrwx 10 nobody users 232 Aug  6  2011 disk12/

drwxrwxrwx  6 nobody users 128 Sep 11  2011 disk13/

drwxrwxrwx 10 nobody users 224 Mar 27  2013 disk14/

drwxrwxrwx 13 nobody users 296 Jan 19 13:50 disk15/

drwxrwxrwx 10 nobody users 224 Apr 13  2013 disk16/

drwxrwxrwx  9 nobody users 200 Jun 18  2013 disk17/

drwxrwxrwx  9 nobody users 200 Nov 11 21:25 disk18/

drwxrwxrwx 10 nobody users 224 Jun 29  2013 disk2/

drwxrwxrwx  8 nobody users 176 Jun 29  2013 disk3/

drwxrwxrwx  8 nobody users 176 Jun 26  2011 disk4/

drwxrwxrwx  8 nobody users 176 Jan  5  2013 disk5/

drwxrwxrwx 10 nobody users 232 Jun  1  2013 disk6/

drwxrwxrwx  6 nobody users 128 Jul  9  2011 disk7/

drwxrwxrwx  6 nobody users 128 Jul 23  2011 disk8/

drwxrwxrwx  7 nobody users 160 Jul 25  2011 disk9/

drwxrwxrwx  4 nobody users  0 Feb 10 17:19 user/

drwxrwxrwx  1 nobody users 272 Jan 19 13:50 user0/

 

 

root@Tower:/mnt/disk1# mount

proc on /proc type proc (rw)

sysfs on /sys type sysfs (rw)

/dev/sda1 on /boot type vfat (rw,noatime,nodiratime,umask=0,shortname=mixed)

nfsd on /proc/fs/nfs type nfsd (rw)

nfsd on /proc/fs/nfsd type nfsd (rw)

/dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md5 on /mnt/disk5 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md6 on /mnt/disk6 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md7 on /mnt/disk7 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md8 on /mnt/disk8 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md9 on /mnt/disk9 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md10 on /mnt/disk10 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md11 on /mnt/disk11 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md12 on /mnt/disk12 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md13 on /mnt/disk13 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md14 on /mnt/disk14 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md15 on /mnt/disk15 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md16 on /mnt/disk16 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md17 on /mnt/disk17 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/md18 on /mnt/disk18 type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

/dev/sdt1 on /mnt/cache type reiserfs (rw,noatime,nodiratime,user_xattr,acl)

shfs on /mnt/user0 type fuse.shfs (rw,nosuid,nodev,noatime,allow_other)

 

 

root@Tower:/etc# cat mtab

proc /proc proc rw 0 0

sysfs /sys sysfs rw 0 0

/dev/sda1 /boot vfat rw,noatime,nodiratime,umask=0,shortname=mixed 0 0

nfsd /proc/fs/nfs nfsd rw 0 0

nfsd /proc/fs/nfsd nfsd rw 0 0

/dev/md1 /mnt/disk1 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md2 /mnt/disk2 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md3 /mnt/disk3 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md4 /mnt/disk4 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md5 /mnt/disk5 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md6 /mnt/disk6 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md7 /mnt/disk7 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md8 /mnt/disk8 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md9 /mnt/disk9 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md10 /mnt/disk10 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md11 /mnt/disk11 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md12 /mnt/disk12 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md13 /mnt/disk13 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md14 /mnt/disk14 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md15 /mnt/disk15 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md16 /mnt/disk16 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md17 /mnt/disk17 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/md18 /mnt/disk18 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

/dev/sdt1 /mnt/cache reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0

shfs /mnt/user0 fuse.shfs rw,nosuid,nodev,noatime,allow_other 0 0

 

shouldn't my shares be shown in here too?

syslog_10022014.txt

Link to comment

So I don't have a very strong grasp on Linux or VMs yet, but I took the day yesterday to attempt the installation of v6 beta 3.  I read through the forums and between instructions of a few people here and Google, I managed to get everything installed.  I have an Ubuntu VM running with Plex, PlexWatch, and PlexWatch/Web.  All of that seems to be running smoothly.  However, I have encountered two problems.

 

First, Xen only seems to see half of the memory I have installed.  If you look at the info in the unRAID webGUI, it shows that there is the full 16GB of memory.  However, if I run xl info or xl top, Xen only shows that I have 8GB of memory.  Therefore, if I try to allocate 6GB or more to the VM, Xen errors out saying it is out of memory.

 

Second, unRAID doesnt won't save my password on a reboot.  I keep setting a password but every time I reboot, the password disappears.

 

Any help would be appreciated.  Thanks for all the hard work.

Link to comment

Shares are not in the mtab file.

 

What is in the directory...

 

/boot/config/shares/

 

?

 

Hi needo, here is what is in my directoy

 

root@Tower:/boot/config/shares# ls -l

total 76

-rwxrwxrwx 1 root root 447 Feb  4 21:53 appdata.cfg.bak*

-rwxrwxrwx 1 root root 493 Apr 13  2013 apps.cfg*

-rwxrwxrwx 1 root root 423 Jul  2  2011 backup.cfg*

-rwxrwxrwx 1 root root 504 Feb  6 21:43 cache_only.cfg.bak*

-rwxrwxrwx 1 root root 422 Jul  3  2011 downloads.cfg*

-rwxrwxrwx 1 root root 447 May 22  2011 ebooks.cfg*

-rwxrwxrwx 1 root root 444 Apr 13  2013 misc.cfg*

-rwxrwxrwx 1 root root 446 Feb 10 17:20 movies.cfg*

-rwxrwxrwx 1 root root 445 Feb  6 22:48 movies.cfg.bak*

-rwxrwxrwx 1 root root 472 Jul 30  2011 music.cfg*

-rwxrwxrwx 1 root root 445 Feb  6 22:49 music.cfg.bak*

-rwxrwxrwx 1 root root 444 Aug  6  2011 photos.cfg*

-rwxrwxrwx 1 root root 446 Feb 10 16:32 series.cfg*

-rwxrwxrwx 1 root root 445 Feb  7 21:54 series.cfg.bak*

-rwxrwxrwx 1 root root 444 Feb 10 20:35 software.cfg*

-rwxrwxrwx 1 root root 444 Aug  6  2011 timemachine.cfg*

-rwxrwxrwx 1 root root 447 May 22  2011 training.cfg*

-rwxrwxrwx 1 root root 443 Jan 19 13:50 vincent.cfg*

-rwxrwxrwx 1 root root 455 Jun 18  2013 xbmc.cfg*

 

I now tried to shutdown and Now I can see all these errors again

 

 

root@Tower:/boot/config/shares# tail /var/log/syslog

Feb 10 22:52:11 Tower emhttp: shcmd (330): rmdir /mnt/user0 |& logger

Feb 10 22:52:11 Tower emhttp: shcmd (331): crontab -c /etc/cron.d -d &> /dev/nul                                    l

Feb 10 22:52:11 Tower emhttp: Retry unmounting user share(s)...

Feb 10 22:52:16 Tower emhttp: shcmd (332): set -o pipefail ; umount /mnt/user |&                                    logger

Feb 10 22:52:16 Tower logger: umount: /mnt/user: not mounted

Feb 10 22:52:16 Tower emhttp: _shcmd: shcmd (332): exit status: 1

Feb 10 22:52:16 Tower emhttp: shcmd (333): rmdir /mnt/user |& logger

Feb 10 22:52:16 Tower logger: rmdir: failed to remove '/mnt/user': Directory not                                    empty

Feb 10 22:52:16 Tower emhttp: shcmd (334): crontab -c /etc/cron.d -d &> /dev/nul                                    l

Feb 10 22:52:16 Tower emhttp: Retry unmounting user share(s)...

 

Link to comment

I'll throw my hat in on the Plex VM issue. I run this in a win7 VM under ESXi at the moment. That VM would be lucky if I've given it more than 4gig of memory although if anyone really cares I can look when I get home. I'm not sure what constitutes a large library but over 1500 movies and probably that many TV shows if not more ought to constitute that I'd think? Plex has no issues in this VM for me, memory and performance appear fine. I just tested both a movie and a TV show streamed over cellular that worked fine with the movie having to be down sampled a great deal I'm sure ;-)

 

I may yet set this up in a VM under Xen but last I tried to set this up under Linux I ran into issues mounting my shares - I use SMB vs NFS which I suppose I should try ;-) bottom line: Plex performance in a VM should be fine if you can run it decently bare metal. Try it and see!

 

PS I'd point out that of course you can crash the server if you run poorly behaving code on the host. This is true for ESX and any other virtualization technology. The host should be protected as much as possible!

 

Sent from my iPad using Tapatalk

Link to comment

 

Second, unRAID doesnt won't save my password on a reboot.  I keep setting a password but every time I reboot, the password disappears.

 

Any help would be appreciated.  Thanks for all the hard work.

 

Thought I was going mad. But I too have this issue.

 

Sent from my Nexus 5 using Tapatalk

You have to set passwords via the webGui.

Link to comment

Ok I completed the new permission script, it completed successfully, but my shares are not back yet.

 

From the syslog, this is the problem:

 

Feb  9 19:13:13 Tower emhttp: shcmd (80): /usr/local/sbin/shfs /mnt/user -disks 16777215  -o noatime,big_writes,allow_other -o remember=330  |& logger
Feb  9 19:13:13 Tower shfs/user: fuse_main exit: 1
Feb  9 19:13:13 Tower logger: fuse: invalid argument `noatime,big_writes,allow_other'

 

That shouldn't happen.  Not sure why it's happening on your system; I will have to try and recreate.

Link to comment

Just want to wrap up the plex issues i was having. Plex is running PERFECT in a VM (ironic's arch VM)! Faster than when it was on Dom0 and 0 ISSUES!! Not one crash, everything is faster from file transfers to plex transcoding. Below is my system readout from my Arch VM running plex (streaming 5 movies to different users) and running a full mumble server with 7 users online. Needless to say we can put the plex issue and the crashes i had to rest. Thank you to everyone !!!! unRAID + Xen = EPIC!

 

CPU       8.4%   Load   8-core   Mem    21.5%  active:   1.62G
user:     6.5%   1 min:   0.37   total: 2.93G  inactive: 1.01G
system:   0.6%   5 min:   1.62   used:   646M  buffers:  17.8M
idle:    91.6%   15 min:  1.64   free:  2.30G  cached:   2.13G

Network    Rx/s    Tx/s   Tasks  129 (277 thr),  2 run, 127 slp,  0 oth
eth0     15.9Mb  7.12Mb
lo       14.3Mb  14.3Mb    VIRT   RES  CPU%  MEM% NAME
                            71M   16M  46.5   0.5 Plex
Disk I/O   In/s   Out/s    1.3G   87M   7.7   2.9 Plex
xvda1         0       0    803M   92M   6.1   3.1 Plex
xvdb        16K       0    107M   13M   4.5   0.4 glances
                           3.2G  123M   3.2   4.1 Plex
Mount      Used   Total       0     0   0.6   0.0 ksoftirqd/0
/         1.58G   13.6G       0     0   0.6   0.0 cifsd
/data     14.3G   96.1G       0     0   0.3   0.0 ksoftirqd/3
_t/tower  5.01T   8.19T    255M    8M   0.3   0.3 murmurd
_fs/nfsd      0       0    1.4G    8M   0.3   0.3 Plex
/run       180K   1.47G    1.1G   31M   0.3   1.0 python
/tmp          0   1.47G     31M    2M   0.0   0.1 /sbin/init

Link to comment

 

Second, unRAID doesnt won't save my password on a reboot.  I keep setting a password but every time I reboot, the password disappears.

 

Any help would be appreciated.  Thanks for all the hard work.

 

Thought I was going mad. But I too have this issue.

 

Sent from my Nexus 5 using Tapatalk

You have to set passwords via the webGui.

 

Well, that was easy.  Thanks.  That solves that problem.  Now I just have to figure out my memory issue and I will be happy.

Link to comment

Just want to wrap up the plex issues i was having. Plex is running PERFECT in a VM (ironic's arch VM)! Faster than when it was on Dom0 and 0 ISSUES!! Not one crash, everything is faster from file transfers to plex transcoding. Below is my system readout from my Arch VM running plex (streaming 5 movies to different users) and running a full mumble server with 7 users online. Needless to say we can put the plex issue and the crashes i had to rest. Thank you to everyone !!!! unRAID + Xen = EPIC!

Thanks to Badger for his hard work in getting this set up!  Remember he's a student & doing this during classes in  his spare time  :)

Link to comment

I have been trying to copy data from one v6 box to another via a Mac.  I tried using SMB, and the performance was not very good, was seeing about 4-5mb/s, so I tried Tom's fix for getting NFS to work, and starting getting pretty good performance, 28mb/sec, but I constainly see stale NFS messages:

 

rsync: readlink "/Volumes/TV/WildKratts-S01E07-PolarBearsDontDance-19953525-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/FamilyGuy-PetersProgress-7434366-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/Tosh0-S05E28-25732390-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/ImaginationMovers-SecondChancePants-827409-0.txt" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/FamilyGuy-8681288-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/SouthPark-MissTeacherBaBoy-9418636-0.edl" failed: Stale NFS file handle (70)

 

I thought it was related to delay in drive spin up, but I manually spun up all the drives, and still see these messages from time to time.

 

Anyone seen this before?

 

 

Link to comment

Just want to wrap up the plex issues i was having. Plex is running PERFECT in a VM (ironic's arch VM)! Faster than when it was on Dom0 and 0 ISSUES!! Not one crash, everything is faster from file transfers to plex transcoding. Below is my system readout from my Arch VM running plex (streaming 5 movies to different users) and running a full mumble server with 7 users online. Needless to say we can put the plex issue and the crashes i had to rest. Thank you to everyone !!!! unRAID + Xen = EPIC!

 

CPU       8.4%   Load   8-core   Mem    21.5%  active:   1.62G
user:     6.5%   1 min:   0.37   total: 2.93G  inactive: 1.01G
system:   0.6%   5 min:   1.62   used:   646M  buffers:  17.8M
idle:    91.6%   15 min:  1.64   free:  2.30G  cached:   2.13G

Network    Rx/s    Tx/s   Tasks  129 (277 thr),  2 run, 127 slp,  0 oth
eth0     15.9Mb  7.12Mb
lo       14.3Mb  14.3Mb    VIRT   RES  CPU%  MEM% NAME
                            71M   16M  46.5   0.5 Plex
Disk I/O   In/s   Out/s    1.3G   87M   7.7   2.9 Plex
xvda1         0       0    803M   92M   6.1   3.1 Plex
xvdb        16K       0    107M   13M   4.5   0.4 glances
                           3.2G  123M   3.2   4.1 Plex
Mount      Used   Total       0     0   0.6   0.0 ksoftirqd/0
/         1.58G   13.6G       0     0   0.6   0.0 cifsd
/data     14.3G   96.1G       0     0   0.3   0.0 ksoftirqd/3
_t/tower  5.01T   8.19T    255M    8M   0.3   0.3 murmurd
_fs/nfsd      0       0    1.4G    8M   0.3   0.3 Plex
/run       180K   1.47G    1.1G   31M   0.3   1.0 python
/tmp          0   1.47G     31M    2M   0.0   0.1 /sbin/init

 

I'm still left to wonder why it was causing memory problems in unraid-dom0?  Someone's first guess might be the FrankenPlex version we run in unRaid-64 as opposed to the release version we can run in a VM.  However, I'm having no trouble so far running FrankenPlex in unRaid64 w/o Xen so I'm not convinced it is a direct line from FrankenPlex to memory problems. 

 

I suppose we won't know for sure until PlexCo releases an official version for us to beat on, but it is important to note that people who do not want to run VMs yet, they can use FrankPlex in unRaid 6.0 w/o Xen.

 

Which makes me think of something else ... what do we want to call unRaid w/o Xen?  How about unRaid-bare vs unRaid-dom0?  We need a clear, consistent, and concise lexicon to avoid confusion

Link to comment

I have been trying to copy data from one v6 box to another via a Mac.  I tried using SMB, and the performance was not very good, was seeing about 4-5mb/s, so I tried Tom's fix for getting NFS to work, and starting getting pretty good performance, 28mb/sec, but I constainly see stale NFS messages:

 

rsync: readlink "/Volumes/TV/WildKratts-S01E07-PolarBearsDontDance-19953525-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/FamilyGuy-PetersProgress-7434366-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/Tosh0-S05E28-25732390-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/ImaginationMovers-SecondChancePants-827409-0.txt" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/FamilyGuy-8681288-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/SouthPark-MissTeacherBaBoy-9418636-0.edl" failed: Stale NFS file handle (70)

 

I thought it was related to delay in drive spin up, but I manually spun up all the drives, and still see these messages from time to time.

 

Anyone seen this before?

 

While this does not answer your question, I would recommend considering a direct rsync client to rsync server connection.  It might be a bit to set it up, but it eliminates all network file protocols and could possibly be faster with the right tunings.

Link to comment

I have been trying to copy data from one v6 box to another via a Mac.  I tried using SMB, and the performance was not very good, was seeing about 4-5mb/s, so I tried Tom's fix for getting NFS to work, and starting getting pretty good performance, 28mb/sec, but I constainly see stale NFS messages:

 

rsync: readlink "/Volumes/TV/WildKratts-S01E07-PolarBearsDontDance-19953525-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/FamilyGuy-PetersProgress-7434366-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/Tosh0-S05E28-25732390-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/ImaginationMovers-SecondChancePants-827409-0.txt" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/FamilyGuy-8681288-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/SouthPark-MissTeacherBaBoy-9418636-0.edl" failed: Stale NFS file handle (70)

 

I thought it was related to delay in drive spin up, but I manually spun up all the drives, and still see these messages from time to time.

 

Anyone seen this before?

 

While this does not answer your question, I would recommend considering a direct rsync client to rsync server connection.  It might be a bit to set it up, but it eliminates all network file protocols and could possibly be faster with the right tunings.

 

I tried mounting the one v6 server with the source data directly to the destination v6 server.  Using cifs, I see the same slow performance, about 4mb/sec. 

 

I tried also using NFS and see about 5-10mb/sec.  I haven't seen the stale nfs messages, but I will let it run via screens and see if I encounter any...

Link to comment

I have been trying to copy data from one v6 box to another via a Mac.  I tried using SMB, and the performance was not very good, was seeing about 4-5mb/s, so I tried Tom's fix for getting NFS to work, and starting getting pretty good performance, 28mb/sec, but I constainly see stale NFS messages:

 

rsync: readlink "/Volumes/TV/WildKratts-S01E07-PolarBearsDontDance-19953525-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/FamilyGuy-PetersProgress-7434366-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/Tosh0-S05E28-25732390-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/ImaginationMovers-SecondChancePants-827409-0.txt" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/FamilyGuy-8681288-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/SouthPark-MissTeacherBaBoy-9418636-0.edl" failed: Stale NFS file handle (70)

 

I thought it was related to delay in drive spin up, but I manually spun up all the drives, and still see these messages from time to time.

 

Anyone seen this before?

 

While this does not answer your question, I would recommend considering a direct rsync client to rsync server connection.  It might be a bit to set it up, but it eliminates all network file protocols and could possibly be faster with the right tunings.

 

I tried mounting the one v6 server with the source data directly to the destination v6 server.  Using cifs, I see the same slow performance, about 4mb/sec. 

 

I tried also using NFS and see about 5-10mb/sec.  I haven't seen the stale nfs messages, but I will let it run via screens and see if I encounter any...

Bring up the Settings/NFS page and then click 'Help'.  This will give you information on the "fuse_remember" Tunable.  Try increasing this value, or setting to -1 to see if this eliminates stale file handles.

Link to comment

Is this caused by V6??, in unmenu I run Smart History, and I have a lot of these messages .... was not there on V5

 

 

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 224 Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 419 Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 441 Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /boot/smarthistory/smarthistory.php on line 710 Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezon

Link to comment

Ok I completed the new permission script, it completed successfully, but my shares are not back yet.

 

From the syslog, this is the problem:

 

Feb  9 19:13:13 Tower emhttp: shcmd (80): /usr/local/sbin/shfs /mnt/user -disks 16777215  -o noatime,big_writes,allow_other -o remember=330  |& logger
Feb  9 19:13:13 Tower shfs/user: fuse_main exit: 1
Feb  9 19:13:13 Tower logger: fuse: invalid argument `noatime,big_writes,allow_other'

 

That shouldn't happen.  Not sure why it's happening on your system; I will have to try and recreate.

 

any clue yet, as I cannot shutdown the unRaid server right now, still can use putty ssh and the monitor, but nothing else really. Webinterface is not responding anymore.

Link to comment

I have been trying to copy data from one v6 box to another via a Mac.  I tried using SMB, and the performance was not very good, was seeing about 4-5mb/s, so I tried Tom's fix for getting NFS to work, and starting getting pretty good performance, 28mb/sec, but I constainly see stale NFS messages:

 

rsync: readlink "/Volumes/TV/WildKratts-S01E07-PolarBearsDontDance-19953525-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/FamilyGuy-PetersProgress-7434366-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/Tosh0-S05E28-25732390-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/ImaginationMovers-SecondChancePants-827409-0.txt" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/FamilyGuy-8681288-0.ts.properties" failed: Stale NFS file handle (70)

rsync: readlink "/Volumes/TV/SouthPark-MissTeacherBaBoy-9418636-0.edl" failed: Stale NFS file handle (70)

 

I thought it was related to delay in drive spin up, but I manually spun up all the drives, and still see these messages from time to time.

 

Anyone seen this before?

 

While this does not answer your question, I would recommend considering a direct rsync client to rsync server connection.  It might be a bit to set it up, but it eliminates all network file protocols and could possibly be faster with the right tunings.

 

I tried mounting the one v6 server with the source data directly to the destination v6 server.  Using cifs, I see the same slow performance, about 4mb/sec. 

 

I tried also using NFS and see about 5-10mb/sec.  I haven't seen the stale nfs messages, but I will let it run via screens and see if I encounter any...

Bring up the Settings/NFS page and then click 'Help'.  This will give you information on the "fuse_remember" Tunable.  Try increasing this value, or setting to -1 to see if this eliminates stale file handles.

That did the trick, it has been running for several hours without any stale nfs handles and getting about 28mb/sec...

 

Thanks...

Link to comment

Ok I completed the new permission script, it completed successfully, but my shares are not back yet.

 

From the syslog, this is the problem:

 

Feb  9 19:13:13 Tower emhttp: shcmd (80): /usr/local/sbin/shfs /mnt/user -disks 16777215  -o noatime,big_writes,allow_other -o remember=330  |& logger
Feb  9 19:13:13 Tower shfs/user: fuse_main exit: 1
Feb  9 19:13:13 Tower logger: fuse: invalid argument `noatime,big_writes,allow_other'

 

That shouldn't happen.  Not sure why it's happening on your system; I will have to try and recreate.

 

any clue yet, as I cannot shutdown the unRaid server right now, still can use putty ssh and the monitor, but nothing else really. Webinterface is not responding anymore.

It's a supposedly "impossible" condition in the code.  Is this a pure-vanilla install?  ie, no addons, plugins, etc?  Booting non-Xen?  Nothing in /boot/extra?

Link to comment

any clue yet, as I cannot shutdown the unRaid server right now, still can use putty ssh and the monitor, but nothing else really. Webinterface is not responding anymore.

 

Run the following commands to shut down your server:

/root/samba stop

umount /dev/md1

umount /dev/md2

umount /dev/md3

umount /dev/md4

(repeat for each md drive)

/root/mdcmd stop

 

If everything worked, you can type "poweroff" to shut down.

Link to comment

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.