On 9/30/20 2:38 AM, Greg Kroah-Hartman wrote:
> On Tue, Sep 29, 2020 at 05:04:32PM -0500, Tony Asleson wrote:
>> I'm trying to figure out a way to positively identify which storage
>> device an error belongs to over time.
>
> "over time" is not the kernel's responsibility.
>
> This comes up every 5 years or so. The kernel provides you, at runtime,
> a mapping between a hardware device and a "logical" device. It can
> provide information to userspace about this mapping, but once that
> device goes away, the kernel is free to reuse that logical device again.
>
> If you want to track what logical devices match up to what physical
> device, then do it in userspace, by parsing the log files.
I don't understand why people think it's acceptable to ask user space to
parse text that is subject to change.
>> Thank you for supplying some feedback and asking questions. I've been
>> asking for suggestions and would very much like to have a discussion on
>> how this issue is best solved. I'm not attached to what I've provided.
>> I'm just trying to get towards a solution.
>
> Again, solve this in userspace, you have the information there at
> runtime, why not use it?
We usually don't have the needed information if you remove the
expectation that user space should parse the human readable portion of
the error message.
>> We've looked at user space quite a bit and there is an inherit race
>> condition with trying to fetch the unique hardware id for a message when
>> it gets emitted from the kernel as udev rules haven't even run (assuming
>> we even have the meta-data to make the association).
>
> But one moment later you do have the information, so you can properly
> correlate it, right?
We could have the information if all the storage paths went through
dev_printk. Here is what we get today when we encounter a read error
which uses printk in the block layer:
{
"_HOSTNAME" : "pn",
"_TRANSPORT" : "kernel",
"__MONOTONIC_TIMESTAMP" : "1806379233",
"SYSLOG_IDENTIFIER" : "kernel",
"_SOURCE_MONOTONIC_TIMESTAMP" : "1805611354",
"SYSLOG_FACILITY" : "0",
"MESSAGE" : "blk_update_request: critical medium error, dev
nvme0n1, sector 10000 op 0x0:(READ) flags 0x80700 phys_seg 3 prio class 0",
"PRIORITY" : "3",
"_MACHINE_ID" : "3f31a0847cea4c95b7a9cec13d07deeb",
"__REALTIME_TIMESTAMP" : "1601471260802301",
"_BOOT_ID" : "b03ed610f21d46ab8243a495ba5a0058",
"__CURSOR" :
"s=a063a22bbb384da0b0412e8f652deabb;i=23c2;b=b03ed610f21d46ab8243a495ba5a0058;m=6bab28e1;t=5b087959e3cfd;x=20528862f8f765c9"
}
Unless you parse the message text you cannot make the association. If
the same message was changed to dev_printk we would get:
{
"__REALTIME_TIMESTAMP" : "1589401901093443",
"__CURSOR" :
"s=caac9703b34a48fd92f7875adae55a2f;i=1c713;b=e2ae14a9def345aa803a13648b95429c;m=7d25b4f;t=5a58d77b85243;x=b034c2d3fb853870",
"SYSLOG_IDENTIFIER" : "kernel",
"_KERNEL_DEVICE" : "b259:917504",
"__MONOTONIC_TIMESTAMP" : "131226447",
"_UDEV_SYSNAME" : "nvme0n1",
"PRIORITY" : "3",
"_KERNEL_SUBSYSTEM" : "block",
"_SOURCE_MONOTONIC_TIMESTAMP" : "130941917",
"_TRANSPORT" : "kernel",
"_MACHINE_ID" : "3f31a0847cea4c95b7a9cec13d07deeb",
"_HOSTNAME" : "pn",
"SYSLOG_FACILITY" : "0",
"_BOOT_ID" : "e2ae14a9def345aa803a13648b95429c",
"_UDEV_DEVLINK" : [
"/dev/disk/by-uuid/22fc262a-d621-452a-a951-7761d9fcf0dc",
"/dev/disk/by-path/pci-0000:00:05.0-nvme-1",
"/dev/disk/by-id/nvme-nvme.8086-4445414442454546-51454d55204e564d65204374726c-00000001",
"/dev/disk/by-id/nvme-QEMU_NVMe_Ctrl_DEADBEEF"
],
"MESSAGE" : "block nvme0n1: blk_update_request: critical medium
error, dev nvme0n1, sector 10000 op 0x0:(READ) flags 0x0 phys_seg 1 prio
class 0",
"_UDEV_DEVNODE" : "/dev/nvme0n1"
}
Journald already knows how to utilize the dev_printk meta data.
One idea that I've suggested along the way is creating a dev_printk
function that doesn't change the message text. We then avoid breaking
people that are parsing. Is this something that would be acceptable to
folks? It doesn't solve early boot where udev rules haven't even run,
but it's better.
Thanks,
Tony
