We've a Linux instance and the root volume would automatically changed to readonly after the machine is running for some time (This is the 3rd times) , and reboot the system solve the issue, but it will appear again.
Test:
echo "" > /tmp/test
-bash: /tmp/test: Read-only file system
And in the syslog (Ubuntu 12.04)
Jul 11 04:15:23 localhost kernel: [7470527.963527] JBD2: Detected IO errors while flushing file data on sda1-8 Jul 11 04:15:23 localhost kernel: [7470528.011196] JBD2: Detected IO errors while flushing file data on sda1-8 Jul 11 04:15:23 localhost kernel: [7470528.041984] JBD2: Detected IO errors while flushing file data on sda1-8 Jul 11 04:15:23 localhost kernel: [7470528.108600] JBD2: Detected IO errors while flushing file data on sda1-8 Jul 11 04:15:23 localhost kernel: [7470528.143191] JBD2: Detected IO errors while flushing file data on sda1-8 Jul 11 04:15:23 localhost kernel: [7470528.244366] JBD2: Detected IO errors while flushing file data on sda1-8 Jul 11 04:15:24 localhost kernel: [7470529.276309] JBD2: Detected IO errors while flushing file data on sda1-8 Jul 11 04:17:30 localhost kernel: [7470655.671781] hv_storvsc vmbus_0_1: cmd 0x2a scsi status 0x2 srb status 0x4 Jul 11 04:17:59 localhost kernel: [7470684.066669] hv_storvsc vmbus_0_1: cmd 0x2a scsi status 0x2 srb status 0x4 Jul 11 04:17:59 localhost kernel: [7470684.066679] hv_storvsc vmbus_0_1: cmd 0x2a scsi status 0x2 srb status 0x4 Jul 11 04:17:59 localhost kernel: [7470684.066682] hv_storvsc vmbus_0_1: cmd 0x2a scsi status 0x2 srb status 0x4 Jul 11 04:17:59 localhost kernel: [7470684.066686] hv_storvsc vmbus_0_1: cmd 0x2a scsi status 0x2 srb status 0x4 Jul 11 04:17:59 localhost kernel: [7470684.066689] hv_storvsc vmbus_0_1: cmd 0x2a scsi status 0x2 srb status 0x4 Jul 11 04:17:59 localhost kernel: [7470684.066692] hv_storvsc vmbus_0_1: cmd 0x2a scsi status 0x2 srb status 0x4 Jul 11 04:17:59 localhost kernel: [7470684.066695] hv_storvsc vmbus_0_1: cmd 0x2a scsi status 0x2 srb status 0x4
It seems the hardware is having issue, anyway, how to solve?
Besides, are there any way to get faster support in this case? (It is because your hardware is having issue..)