Page MenuHomeFreeBSD

cam: Reduce overly long timeout values for initial device probing
Needs ReviewPublic

Authored by imp on Sep 8 2025, 5:01 PM.
Tags
None
Referenced Files
Unknown Object (File)
Thu, Oct 16, 1:29 AM
Unknown Object (File)
Wed, Oct 8, 11:27 PM
Unknown Object (File)
Fri, Oct 3, 12:07 PM
Unknown Object (File)
Fri, Oct 3, 8:50 AM
Unknown Object (File)
Thu, Oct 2, 4:17 PM
Unknown Object (File)
Tue, Sep 30, 8:29 AM
Unknown Object (File)
Fri, Sep 26, 7:35 PM
Unknown Object (File)
Fri, Sep 26, 4:39 PM
Subscribers

Details

Reviewers
ken
mav
Group Reviewers
cam
Summary

Currently, we have very long timeouts for the initial probing
commands. However, these are not appropriate for modern (post 2010) SCSI
disks. Sandards since SPC3 state that these commands should not wait for
media access. Since we retry them several times during the initial bus
scan, these delays can delay the boot by minutes (5 minutes per errant
disk in our expereince). These delays don't help and only hurt, so
reduce the TESTUNITREADY, INQUIRY and MODESENSE commands (during the
initial probe). Provide sysctl/tuneables to change the time for these
and also the REPORTLUNS commands for people that might need to adjust
them for devices that violate this belief but none-the-less work with
longer timeouts.
kern.cam.tur_timeout (default was 60s, now 1s)
kern.cam.inquiry_timeout (default was 60s, now 1s)
kern.cam.reportluns_timeout (default is 60s)
kern.cam.modesense_timeout (default was 60s, now 1s)

Sponsored by: Netflix

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 66896
Build 63779: arc lint + arc unit