July 6, 201214 yr Had a strange one today. I ran a non correcting parity-sync last night, expecting it would finish within 28000 seconds or so. My first parity sync since upgrading. I've attached a syslog. No issues, no drive errors or hardware errors. Did notice a write occurred to the array ~ 8 hours into the parity check - see attached images. 4.7- Repeatable since bulid (Nov '10) - Line 2368: Jun 1 07:57:01 Tower kernel: md: sync done. time=28620sec rate=68256K/sec Line 2369: Jun 1 07:57:01 Tower kernel: md: recovery thread sync completion status: 0 5RC5-r8168 - 42MB/s Line 1: 2012-07-05 13:09:34 warning 192.168.1.108 kern kernel kernel: md: recovery thread sync completion status: 0 Line 2: 2012-07-05 13:09:34 warning 192.168.1.108 kern kernel kernel: md: sync done. time=47463sec Any ideas? syslog.tgz.txt
July 6, 201214 yr If you have a SAS MV8 card, might need to go down to B14. I had parity speed issues on the latest RCs with them.
Archived
This topic is now archived and is closed to further replies.