Hello all,

 

my unraid server just stopped sharing it's shares. Yesterday everything was working as expected. The server was shut down normally and without problems. Today xbmc couldn't find the shares. A quick check with a windows machine confirmed that the server wasn't sharing. I logged onto the server and was glad to see that all files where still there. But the shares were not mounted under /mnt/user/ . A check with ps revealed that shfs was not running. The syslog (see attachment) showed the following lines:

Dec 10 14:11:43 Kanga emhttp: shcmd (34): mkdir /mnt/user
Dec 10 14:11:43 Kanga emhttp: shcmd (35): /usr/local/sbin/shfs /mnt/user -disks 16777214 -o noatime,big_writes,allow_other -o remember=0  |& logger
Dec 10 14:11:43 Kanga logger: fuse: invalid argument `16777214'

It is quite clear that emhttp tries to start shfs with some invalid arguments. If I start shfs by hand using:

/usr/local/sbin/shfs /mnt/user -o noatime,big_writes,allow_other -o remember=0  |& logger

leaving out the offending argument, everything works ok. Where does the value for the disks argument come from? What can I do to fix this situation?

unraid_syslog.txt

Some further findings:

I had a file named shfs in the root directory of the flash drive. (Don't ask why. I copied some scripts from a backup of an old version of unraid to the flash and must have copied shfs as well.)

Renaming the file and rebooting made unraid act normally again. I don't really understand why. As shfs was started by emhttp (and later manually) with the full path, the file in the root of the flash drive shouldn't have interfered here.

Why is shfs influenced by some file in an unrelated path? Is this some kind of plugin or hooking mechanism?

Maybe someone with insight into the source code could shed some light here.