Thread (11 messages) 11 messages, 4 authors, 2011-08-30

Re: [-v3 PATCH 0/3] Persistent device name using alias

From: Tejun Heo <tj@kernel.org>
Date: 2011-08-27 10:27:01
Also in: lkml

(cc'ing Kay)
Hello,

On Sat, Aug 27, 2011 at 07:15:25PM +0900, Nao Nishijima wrote:
Our concern is the failure analysis. For example, when the disk failure
happened, we need to identify the disk from kernel log.

Kernel messages are output to serial console when kernel crashes.
It's so hard to convert a device name to the alias. Thus the script
can't always convert the name.
Hmm... I don't follow.  Why wouldn't it be able to?  All the
informations are in the log.  It is messy but it's there.  If you want
more structured information, u{dev|disks} already maintain device
libarary - what maps to what, connected how with what attributes and
so on.  Sending them off to the log machine as device hotplug events
occur and consulting it when post-processing log message would work
fine.  All you need is just some python scripting.  I don't really see
much point in messing with device names directly.  The only thing is
that the raw log would be prettier.  I don't think that is useful
enough to justify changing kernel device names.

Thanks.

-- 
tejun
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help