Displaying 2 results from an estimated 2 matches for "vhost03".
Did you mean:
vhost01
2017 Mar 10
3
CentOS-6.8 fsck report Maximal Count
...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?
>
> 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
I am running an extended SMART test on the drive at the moment. I
suspect...
2017 Mar 09
1
CentOS-6.8 fsck report Maximal Count
...stem 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.
However, this action did not remove the error. The host system log
files had this to say about fsck:
/var/log/messages:Mar 9 08:34:48 vhost03 kernel: EXT4-fs (dm-6):
warning: maximal mount count reached, running e2fsck is recommended
in /dev I see this:
brw-rw----. 1 root disk 253, 6 Mar 9 08:34 dm-6
But, this device has nothing whatsoever to do with the kvm guests:
ll /dev/vg_vhost03/ | grep dm-6
lrwxrwxrwx. 1 root root 7 Mar...