James B. Byrne wrote:
On Thu, March 9, 2017 09:46, John Hodrien wrote:
On Thu, 9 Mar 2017, James B. Byrne wrote:
This indicated that a bad sector on the underlying disk system might be the source of the problem. The guests were all shutdown, a /forcefsck file was created on the host system, and the host system remotely restarted.
fsck's not good at finding disk errors, it finds filesystem errors.
If not fsck then what?
fsck run with -c, which forces badblocks to run. Or you can run that directly.
If it was a real disk issue, you'd expect matching errors in the host logs.
Yes, there are:
Mar 9 09:14:13 vhost03 kernel: end_request: I/O error, dev sda, sector 1236929063 Mar 9 09:14:30 vhost03 kernel: end_request: I/O error, dev sda, sector 1236929063 Mar 9 09:14:48 vhost03 kernel: end_request: I/O error, dev sda, sector 1236929063
Looks like only one sector's bad. Running badblocks should, I think, mark that sector as bad, so the system doesn't try to read or write there. I've got a user whose workstation has had a bad sector running for over a year. However, if it becomes two, or four, or 64 sectors, it's replacement time, asap. <snip> mark