Early this morning a monthly parity check kicked off automatically.  It was reporting a speed of about 3,000 KB/sec, with an estimated completion time of 8.8 days.  Thinking perhaps it was a memory issue, I started killing off unneeded processes, but that didn't seem to fix the problem.  I ended up canceling the check, rebooting, and starting up the parity check again.  Now the speed is more to my liking, starting at 45,000 and now it's currently at 95,000 KB/sec.

 

My question is, would lack of memory cause an uber slow parity check?  Perhaps a memory leak somewhere?  Running 4.6-rc3, HW specs in my sig.  I can post my syslog, but I didn't see anything abnormal from the point of the check kicking off. 

 

Thanks in advance!

Did you capture a syslog before rebooting?

Not manually, but unRAID saved the log to the flash drive during reboot.

 

http://dl.dropbox.com/u/71425/syslog-20101201-005317.txt

 

The parity check I kicked off after reboot concluded this morning without issue.  At least that's good!