Before a grow on a 8 TB RAID5, I am currently doing an e2fsck.
While the RAID was running w/o issues before (I switched from Ubuntu to CentOS 5.4 because I needed a specific hardware driver), the e2fsck initially turned up a boatload of errors (nohup.out is 7 GB), but after 5 days of continuous fscking, there have been no more outputs into the logs for nearly 2 days even though the process is still running at 100% CPU and 1.5G RAM. I tried an killall -USR1 e2fsck, but I still get no further outputs in my log.
Is it safe to kill e2fsck and retry with the -C option or will I make things worse? I have looked into the running times of e2fsck but from what I read by now it should have finished.