I think indeed it was a RAM issue. After some cache-flushing, e2fsck on the file system with the checksum errors reported no errors, even though there wasn't even a reboot in between. (Then I discovered the "e2fsck -F" flag, which would have been a lot simpler than what I did instead. Oh, well.) Looking in the BIOS, I found some suspicious timing parameters that might be responsible, and reset them to stock. I'll know for sure if the problem stays away for a month, but in the mean time, thank you everyone for your help and patience, and consider the matter resolved unless I find more problems. Sorry for the false alarm. -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
