{"issue":{"created_at":"2011-11-29T01:25:36Z","state":"open","updated_at":"2011-11-29T01:25:36Z","user":{"gravatar_id":"7fbf46d97324d6a5649d1ff2e3f6663d","id":346306,"url":"https://api.github.com/users/Rudd-O","avatar_url":"https://secure.gravatar.com/avatar/7fbf46d97324d6a5649d1ff2e3f6663d?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","login":"Rudd-O"},"comments":0,"body":"For every disk device that ZFS manages:\r\n\r\nOn Fri, 2011-11-25 at 11:12 +0100, e-t172 wrote:\r\nOn 2011-11-25 11:02, Fajar A. Nugraha wrote:\r\n> > For zfs to work properly:\r\n> > - a drive needs to be report quickly that it failed\r\n> > - zfs needs to know that the drive failed, and kick it out of the pool\r\n> > (possibly activating hot spare, if available)\r\n> >\r\n> > The problem is some drives (your HDD might be among those) will retry\r\n> > for a LOOOONG time reading/writing to a bad sector before if it gives\r\n> > up. And linux's driver will also spend lots of time retrying.\r\n> \r\n> Maybe reducing /dev/block/*/device/timeout would alleviate this issue?\r\n> \r\n> \r\n\r\nIt'd be appropriate in case the device is just being... uhh... quite literally retarded.  Five seconds?  Ten seconds?  Should be enough in contrast to the minutes- or hours-long timeouts.\r\n\r\nDonno if this will fix the \"kernel retries reads\" problem (which fundamentally we need to solve in the linux kernel), but this might help.\r\n\r\nI'd advise to adjust the timeout even in the case of disk partitions being used rather than whole disks.  Remember that most of us who use zfs-on-root have no choice but to use ZFS on disk partitions because of /boot.","assignee":null,"labels":[],"id":2375873,"number":471,"pull_request":{"patch_url":null,"html_url":null,"diff_url":null},"title":"Reduce timeout on disks","closed_at":null,"html_url":"https://github.com/zfsonlinux/zfs/issues/471","url":"https://api.github.com/repos/zfsonlinux/zfs/issues/471","milestone":null},"action":"opened"}