For the past few days, every morning I wake up to a completely crashed server.  I believe it's mover related, as if I manually invoke the mover, i experience a crash as well.  Attached is a syslog. 

 

The only change to my server in the past while was the replacement of a 2tb drive with a 3tb drive (disk3).  Everything else on the server functions normally until the mover is invoked.  Running RC3 (I tried upgraded to RC6 but had the same problems so went back to RC3)

 

Does anyone have any suggestions?  Server specs are in my signature (kirk server). 

syslog.txt

You are getting a kernel "Oops".    Now, normally that can only happen with buggy kernel code, OR, bad memory, OR, I've seen file system corruption cause the kernel to Oops.

 

You can try the following:

 

Perform a memory test, for at least several cycles, preferably overnight.   

Check the file-systems on each of your data disks following the instructions in the wiki:

http://lime-technology.com/wiki/index.php/Check_Disk_Filesystems

 

If you are running a number of add-ons, it is possible to run out of "low memory" if too much is being run at a time.  You might try stopping all the add-ons before running  "mover"

I have seen this happen for 2 different reasons. 1) when there is not enought memory, if you have the option to grab additional memory from another system (just to test it out). 2) Xeon processors running unRAID physical, not under virtulization.

 

Thanks for the advice.  I'll see if I have any extra memory kicking around that is compatible with this motherboard (damn picky supermicro motherboards).  I'm also running reiserfchk as I type this, but it'll take a while.  I'm going away for the weekend, so I'll probably leave memtest running then as well.

 

The strange thing is that this system has been running for about a year and a half with no problems, then all of a sudden these problems start.

 

The add ons I have running are apcupsd, sabnzbd, couchpotato & sick beard.  I will try disabling them as well.

memtest ran fine with no errors overnight. 

 

I did seem to cure the problem as I noticed it would only crash when it was going to move the hidden .AppleDB files in a few directories on the cache drive.  I removed those .AppleDB folders and have not had a problem since. 

 

Now the mover works, however it is showing the following when the mover is running in my syslog:

 

Jul 15 15:35:08 Kirk logger: .d..t.....x TV Shows/

Jul 15 15:35:08 Kirk logger: Cannot stat file /proc/7922/fd/3: No such file or directory

Jul 15 15:35:08 Kirk logger: Cannot stat file /proc/7922/fd/5: No such file or directory

Jul 15 15:35:08 Kirk logger: Cannot stat file /proc/7922/fd/6: No such file or directory

Jul 15 15:35:08 Kirk logger: Cannot stat file /proc/7922/fd/7: No such file or directory

Jul 15 15:35:08 Kirk logger: Cannot stat file /proc/7922/fd/9: No such file or directory

Jul 15 15:35:08 Kirk logger: Cannot stat file /proc/7922/fd/10: No such file or directory

 

which if I view the folder it shows that it points to various files that were in the .AppleDB folder that was removed.  Am I able to just remove the 7922 folder from the /proc directory?

Never mind, I just killed process 7922 and its gone