Recently freed up a disk so I could use it as a cache drive, but every time the mover runs it takes my system down with Kernel oops messages in syslog.
I saw this thread: http://lime-technology.com/forum/index.php?topic=23406.0 but I'm getting different behaviour.
Here's a syslog from me rebooting the system (it was a hard reboot), starting the array (it forces a parity check because of the hard reboot), and running the mover script (while parity check is running, though that shouldn't matter, right?). Looks like shfs segfaults and then the kernel oopses itself into oblivion shortly after this (normally as soon as another process tries to talk to the array).
I've put it on Gist because it exceeded the post length limit here: https://gist.github.com/raw/3e6e3784880779c04561/08fffa463adbee6a8663bdc2f23a167a48aa8990/gistfile1.txt
A little further digging shows that the /mnt/user0 becomes completely unusable after running mover. Here's a before:
root@seraphim:~# ls -l /mnt
total 0
drwxrwx--- 9 nobody users 272 2012-12-14 00:33 cache/
drwxrwx--- 12 nobody users 360 2012-12-14 00:33 disk1/
drwxrwx--- 7 nobody users 152 2012-09-11 05:55 disk2/
drwxrwx--- 7 nobody users 232 2012-11-25 20:02 disk3/
drwxrwx--- 7 nobody users 216 2012-09-13 18:05 disk4/
drwxrwx--- 1 nobody users 272 2012-12-14 00:33 user/
drwxrwx--- 1 nobody users 360 2012-12-14 00:33 user0/
and after running mover:
root@seraphim:~# ls -l /mnt
/bin/ls: cannot access /mnt/user0: Transport endpoint is not connected
total 0
drwxrwx--- 9 nobody users 272 2012-12-14 00:33 cache/
drwxrwx--- 12 nobody users 360 2012-12-14 00:33 disk1/
drwxrwx--- 7 nobody users 152 2012-09-11 05:55 disk2/
drwxrwx--- 7 nobody users 232 2012-11-25 20:02 disk3/
drwxrwx--- 7 nobody users 216 2012-09-13 18:05 disk4/
drwxrwx--- 1 nobody users 272 2012-12-14 00:33 user/
d??? ? ? ? ? ? user0/