大网数据广告活动
服务器运维问答

Drawbacks of setting a high I/O timeout?

· 52CE 我爱测

I'm working on several Linux VMs whose partitions are mounted on a NetApp NAS. This NAS periodically experiences a very high iowait which causes the VM disks to switch to read-only mode, crash, or be corrupted. On the VMware KB i…

问题原文

原帖链接 · dr_ · CC BY-SA 3.0

I'm working on several Linux VMs whose partitions are mounted on a NetApp NAS. This NAS periodically experiences a very high iowait which causes the VM disks to switch to read-only mode, crash, or be corrupted.

On the VMware KB it is suggested to increase the timeout value as a palliative cure:

echo 180 > /sys/block/sda/device/timeout

What could be the negative effects of setting a very high timeout (1800 or more)? The way I see it, the risk is that the delayed writes accumulate and fill up the I/O write buffer, crashing the system. Therefore this solution might be worse than the issue.

已采纳解答

原帖链接 · shodanshok · CC BY-SA 3.0

Most writes, being cached in the OS dirty pagecache, are already completed asynchronously. In other word, they often have nothing to do with device timeout.

However, reads and synchronized writes requires immediate attention from the underlying block device, and this is the very reason your filesystem switches to read-only mode (it can not write its journal to disk).

Increasing I/O wait time should have no bad impact, but it is not a silver bullet. For example, a database can go in read-only mode even it the underlying filesystem remain in read-write mode.

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2015-11-16)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。