From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Linus Walleij <linus.walleij@linaro.org>,
linux-hwmon@vger.kernel.org, Jean Delvare <jdelvare@suse.com>,
Linux Doc Mailing List <linux-doc@vger.kernel.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-scsi@vger.kernel.org, linux-ide@vger.kernel.org,
Chris Healy <cphealy@gmail.com>
Subject: Re: [PATCH 1/1] hwmon: Driver for temperature sensors on SATA drives
Date: Tue, 17 Dec 2019 22:39:26 -0500 [thread overview]
Message-ID: <yq14kxygv4h.fsf@oracle.com> (raw)
In-Reply-To: <c5689126-46bc-b551-11d7-e5bd8c01f82c@roeck-us.net> (Guenter Roeck's message of "Mon, 16 Dec 2019 20:20:57 -0800")
Guenter,
> If there are 100 physical drives, you would actually want to see the
> temperature of each drive separately, as one of them might be
> overheating due to some internal failure.
Yep. However, for "big boxes" you'll typically get that information from
SAF-TE or SES enclosure services and not from the drive itself.
SES allows you to monitor power supplies, drive bays, hot swap events,
thermals, etc. We have a SES driver in SCSI that exposes all these
things in sysfs. It is not currently tied into hwmon.
> If the storage array is represented to the system as single huge
> physical drive, which is then split into logical entities not related
> to physical drives, I guess that would represent a problem for system
> management overall.
Yep. That's why there's dedicated plumbing in smartmontools to handle
various RAID controller interfaces for accessing physical drive
information. It's typically highly vendor-specific.
> I would not mind to tie the hardware monitoring device to something
> else than the scsi device if the scsi device does not always have a
> physical representation. Is there a way to determine if a scsi device
> is virtual or real ?
Not really. Target is usually a pretty good approximation, although some
arrays introduce virtual targets because of limited LUN (scsi_device)
numbering capabilities. However, arrays generally don't support per-LUN
temperature because it makes no sense.
I'm trying to gauge how much a pain potentially redundant sensors would
be for userland monitoring tooling vs. how many oddball devices we'd not
be able to support if we were to use scsi_target as parent (or restrict
the sensor binding to LUN 0).
--
Martin K. Petersen Oracle Linux Engineering
next prev parent reply other threads:[~2019-12-18 3:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-09 5:21 [PATCH 0/1] Summary: hwmon driver for temperature sensors on SATA drives Guenter Roeck
2019-12-09 5:21 ` [PATCH 1/1] hwmon: Driver " Guenter Roeck
2019-12-09 5:28 ` Randy Dunlap
2019-12-09 6:00 ` Guenter Roeck
2019-12-09 17:08 ` Bart Van Assche
2019-12-09 19:20 ` Guenter Roeck
2019-12-10 16:10 ` Bart Van Assche
2019-12-12 22:33 ` Linus Walleij
2019-12-12 23:21 ` Martin K. Petersen
2019-12-13 4:18 ` Guenter Roeck
2019-12-17 2:47 ` Martin K. Petersen
2019-12-17 4:20 ` Guenter Roeck
2019-12-18 3:39 ` Martin K. Petersen [this message]
2019-12-11 4:08 ` [PATCH 0/1] Summary: hwmon driver " Martin K. Petersen
2019-12-11 5:57 ` Guenter Roeck
2019-12-17 2:35 ` Martin K. Petersen
2019-12-17 3:57 ` Guenter Roeck
2019-12-17 5:50 ` Damien Le Moal
2019-12-17 15:47 ` Guenter Roeck
2019-12-18 3:42 ` Martin K. Petersen
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=yq14kxygv4h.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=cphealy@gmail.com \
--cc=jdelvare@suse.com \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@roeck-us.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).