Hi, thanks for the reply... I guess I'm so far as well, but my question is targetted at understanding the realworld implication of the kernel software memory scrubber.
That is, in looking through the code a bit I notice that if hardware ECC is active the software scrubber is disabled. It is also disabled in absence of ECC memory (or unmatched ECC memory). In my particular case: bash-4.0# echo "memscrub_scans_done/U" | mdb -k memscrub_scans_done: memscrub_scans_done: 1985 It appears not to be disabled. My question, I guess, put differently is if it _is_ enabled does it indeed do something useful in the sense of error detection? That is, if it is enabled but *cannot* determine anything related to ECC, _why_ is it running in the first place? That is, if ECC is crippled then the software scrubber gives false impression of doing something useful and is perhaps a bug. On the other hand, if it *can* determine ECC (not crippled), then can we conclude that it is effective [enough] to be able to run as a small and reasonably reliable server? That is, correct correctable errors and be able to log memory errors for eventual action... cheers -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
