From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 215704] New: Trouble locating documentation related to disk read timeout /sys/block/*/device/timeout OR /sys/devices/**/timeout
Date: Sun, 20 Mar 2022 01:57:22 +0000 [thread overview]
Message-ID: <bug-215704-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215704
Bug ID: 215704
Summary: Trouble locating documentation related to disk read
timeout /sys/block/*/device/timeout OR
/sys/devices/**/timeout
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: enhancement
Priority: P1
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: mjevans1983@gmail.com
Regression: No
I've been unable to locate Documentation that matches some locations within
sysfs.
/sys/block/*/device/timeout
/sys/devices/**/timeout
They all appear to cat a value of 30. However an initial experiment with this
value appears to diverge from assumptions I had made.
My context is related to TLER
smartctl -l scterc,${TIMEOUT_SEC}0,${TIMEOUT_SEC}0 /dev/sdX
I have a software RAID (ZFS in this case) which isn't interacting the way it
expects with underlying hardware. I was hoping to find a manual that might
explain how the block device tunable fields such as 'timeout' are intended to
be utilized and tuned.
I didn't see anything obvious in search of text and 'reStructuredText' files
with the obvious keyword:
https://github.com/torvalds/linux/search?l=Text&p=6&q=timeout
https://github.com/torvalds/linux/search?l=reStructuredText&p=16&q=timeout
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-03-20 1:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 1:57 bugzilla-daemon [this message]
2022-03-20 18:49 ` [Bug 215704] Trouble locating documentation related to disk read timeout /sys/block/*/device/timeout OR /sys/devices/**/timeout bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-215704-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.