Hi,
We have a strange problem of our RHEL servers turning Read-only with the following errors:
===========================
sd 0:0:0:0: timing out command, waited 60s
Buffer I/O error on device sda2, logical block 36435
lost page write due to I/O error on sda2
Aborting journal on device sda2.
EXT3-fs error (device sda2) in ext3_reserve_inode_write: Journal has aborted
journal commit I/O error
EXT3-fs error (device sda2) in ext3_dirty_inode: Journal has aborted
ext3_abort called.
EXT3-fs error (device sda2): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
journal commit I/O error
=======================
We have set the SCSI timeout to 180s as per the recommendation from Red Hat and it's still timing out at 60s. Anyone know what this happens ?
Here are the Red hat recommended settings:
---------------------------------------------------------------------------------
[root@bash]# mount
/dev/sdb2 on / type ext3 (rw,barrier=1)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw,barrier=1)
/dev/sdd on /apps type ext3 (rw,barrier=1)
/dev/sdc on /opt type ext3 (rw,barrier=1)
[root@bash]# grep 180 /etc/udev/rules.d/*
/etc/udev/rules.d/50-udev.rules: RUN+="/bin/sh -c 'echo 180 > /sys$$DEVPATH/timeout'"
[root@bash# cat /sys/block/*/device/timeout
180
180
180
180
--------------------------------------------
We have applied the setting above but still it's timing out at 60s and Red Hat recommends to check with Microsoft. Is there any setting in Linux Integration tools on Hyper-V which override this settings ?
What are the best methods to troubleshoot the issues with SCSI on guest OS on Hyper-V level ?
Regards
Root :)
