I can tell you for a certainty that typing control-C to interrupt fsck will not cause I/O errors in dmesg. If you are consistently getting I/O errors in dmesg after typing control-C, something else is going on.
You're going to need to say more about these sets of desktop machines, and how the hardware has been treated. Fsck shouldn't be running if the system was shutdown cleanly. Why are all of these machines running fsck? Do you have unclean power, so the machines are crashing due to power failures? I've seen cases where the neutral got disconnected from ground at the transformer, so half the machines were seeing around 60-70 volts, and half the machines in the cluster were seeing 180 volts between hot and neutral, thanks to a floating neutral. I don't know that there is a power issue, but if you have multiple machines showing I/O failures, across multiple machines, there is something going on, and my guess is that it's far more than software related. Maybe a bad batch of drives? Maybe an unethical hardware provider? But my suggestion is to run hardware diagnostics first, before you do anything else. -- fsck destroys data on interruption https://bugs.launchpad.net/bugs/521293 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
