b0bje
Dabbler
- Joined
- Sep 16, 2011
- Messages
- 16
A while ago I tuned sysctl.conf to allow my cpu cores to go to c3 and c2 respectively.
Everything seemed fine, but a few days after I notice my nightly scrub (I'm paranoid)
was beginning to report errors on my raidz pool. Errors it corrected, luckily.
For several consecutive days it found, reported and fixed errors.
I removed the cx_reported and since then no errors on my disks anymore.
I would prefer not to test my theory and reinsert the dev.cpu.?.cx_supported lines,
any idea if cpu powersaving can cause the above or should I be looking more closely
at other hardware.
Oh, and aside from "zpool status" the above errors were never accompanied by any
system or kernel error messages. If it was another harware failure it wasn't logged.
any and all input welcome !
Everything seemed fine, but a few days after I notice my nightly scrub (I'm paranoid)
was beginning to report errors on my raidz pool. Errors it corrected, luckily.
For several consecutive days it found, reported and fixed errors.
I removed the cx_reported and since then no errors on my disks anymore.
I would prefer not to test my theory and reinsert the dev.cpu.?.cx_supported lines,
any idea if cpu powersaving can cause the above or should I be looking more closely
at other hardware.
Oh, and aside from "zpool status" the above errors were never accompanied by any
system or kernel error messages. If it was another harware failure it wasn't logged.
any and all input welcome !
