Linux hosts on VMware and disk subsystem timeouts.
This is perhaps a tough one to answer but it nags me sometimes.
When you have a Linux guest on a VMware host where the disk subsystem is under heavy load and takes to long to answer the Linux guest often remounts the disk as read-only.
My ventures into the various documentation, interweb and support sites hasnt given me a better solution than to throw more hardware at the problem.
I use "tune2fs -e continue /dev/sda" to avoid having the disk remounted RO in a vmware enviroment but i suspect it will continue on other faliures than timeouts then.
Is it possible to tune the timeout for disks or is that something thats hardcoded in the drivers?
Comments
-
I cant say im sure but i think the value for /sys/block/$i/device/timeout effect command timeouts only. Other kinds of timeouts arent handled by this i think. The default values i have seen has been 60 seconds with udev and 30 without but the timeouts that triggers the remounts has been much shorter than this.
The only thing that has worked for me has been to use tune2fs but that doesnt work for eg. NSS filesystems on Novell Open Enterprise on a VMware guest.0 -
Your system might be hitting this :
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=51306
let me know0 -
I would be curious to see what the host's storage is up to. Usually in a virtual environment the kernel will remount the filesystem to r/o to protect itself when errors start showing up. You see this when the SCSI ibas having trouble due to whatever reason. Feedback comes back to the kernel and if it does not know how to handle the errors it protects itself.
Most newer kernels of the 2.6.16 has been tweaked in error handling. However, if you are still having trouble you can add barrier support. The barrier transaction is a method the CPU uses to confirm messages are being received by peripheral devices. Usually they are sent when response have not been received.
From one of Novell's TID (Technical Information Document) explains it pretty well:When a kernel update (as discussed above) is not an option, the problem can als be worked around by explicitly disabling barrier support for the affected filesystems, e.g. by specifying
barrier=0
in /etc/fstab's mount options field for the affected filesystems.
Error handling code in the ext3 filesystem code is not properly handling the case where a device has stopped to accept barrier requests, which can happen with software RAID devices, LVM devices, device-mapper devices and with third party multipathing software like EMC PowerPath.0 -
-
@tuxmania said:
This is perhaps a tough one to answer but it nags me sometimes.When you have a Linux guest on a VMware host where the disk subsystem is under heavy load and takes to long to answer the Linux guest often remounts the disk as read-only.
My ventures into the various documentation, interweb and support sites hasnt given me a better solution than to throw more hardware at the problem.
I use "tune2fs -e continue /dev/sda" to avoid having the disk remounted RO in a vmware enviroment but i suspect it will continue on other faliures than timeouts then.
Is it possible to tune the timeout for disks or is that something thats hardcoded in the drivers?
That's a good question. I'll have to do some research --- ok. This is from an entry I found in the VMware user forums that might help.
0
Categories
- 10.1K All Categories
- 35 LFX Mentorship
- 88 LFX Mentorship: Linux Kernel
- 504 Linux Foundation Boot Camps
- 279 Cloud Engineer Boot Camp
- 103 Advanced Cloud Engineer Boot Camp
- 48 DevOps Engineer Boot Camp
- 41 Cloud Native Developer Boot Camp
- 2 Express Training Courses
- 2 Express Courses - Discussion Forum
- 1.8K Training Courses
- 17 LFC110 Class Forum
- 5 LFC131 Class Forum
- 19 LFD102 Class Forum
- 148 LFD103 Class Forum
- 13 LFD121 Class Forum
- 61 LFD201 Class Forum
- LFD210 Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum
- 23 LFD254 Class Forum
- 569 LFD259 Class Forum
- 100 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 1 LFS145 Class Forum
- 23 LFS200 Class Forum
- 739 LFS201 Class Forum
- 1 LFS201-JP クラス フォーラム
- 1 LFS203 Class Forum
- 45 LFS207 Class Forum
- 298 LFS211 Class Forum
- 53 LFS216 Class Forum
- 46 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 10 LFS244 Class Forum
- 27 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- 131 LFS253 Class Forum
- 997 LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 87 LFS260 Class Forum
- 126 LFS261 Class Forum
- 31 LFS262 Class Forum
- 79 LFS263 Class Forum
- 15 LFS264 Class Forum
- 10 LFS266 Class Forum
- 17 LFS267 Class Forum
- 17 LFS268 Class Forum
- 21 LFS269 Class Forum
- 200 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- 212 LFW211 Class Forum
- 154 LFW212 Class Forum
- 899 Hardware
- 217 Drivers
- 74 I/O Devices
- 44 Monitors
- 115 Multimedia
- 208 Networking
- 101 Printers & Scanners
- 85 Storage
- 749 Linux Distributions
- 88 Debian
- 64 Fedora
- 14 Linux Mint
- 13 Mageia
- 24 openSUSE
- 133 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 355 Ubuntu
- 473 Linux System Administration
- 38 Cloud Computing
- 69 Command Line/Scripting
- Github systems admin projects
- 94 Linux Security
- 77 Network Management
- 108 System Management
- 49 Web Management
- 63 Mobile Computing
- 22 Android
- 27 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 528 Off Topic
- 127 Introductions
- 213 Small Talk
- 20 Study Material
- 794 Programming and Development
- 262 Kernel Development
- 498 Software Development
- 923 Software
- 258 Applications
- 182 Command Line
- 2 Compiling/Installing
- 76 Games
- 316 Installation
- 53 All In Program
- 53 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)