public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nao Nishijima <nao.nishijima.xt@hitachi.com>
To: Tejun Heo <tj@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
	Jens Axboe <axboe@kernel.dk>,
	James.Bottomley@HansenPartnership.com,
	dle-develop@lists.sourceforge.net,
	Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>,
	yrl.pp-manager.tt@hitachi.com, kay.sievers@gmail.com
Subject: Re: [-v3 PATCH 0/3] Persistent device name using alias
Date: Sat, 27 Aug 2011 21:54:29 +0900	[thread overview]
Message-ID: <4E58E905.4020704@hitachi.com> (raw)
In-Reply-To: <20110827102655.GJ2632@htj.dyndns.org>

Hello,

(2011/08/27 19:26), Tejun Heo wrote:
> (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

In many cases, the script is able to convert the name. However there is
the special case that the logs do not exist in memory and disk due to
the crash except console.


> 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.

A kernel device names (e.g. sda) is not useful information because it
doesn't always point the same disk at each boot-up time.

An alias is just an option and provides the ability to give all
kernel devices a "preferred name".

By default, dev_printk's will show a kernel device name. They show an
alias only when the user assigns a "preferred name" to an alias.
Even if the persistend device name is used, the device names in logs are
different from the name that the users are using. So, an alias helps the
user identify the disk.


Best regards,

-- 
Nao NISHIJIMA
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., YOKOHAMA Research  Laboratory
Email: nao.nishijima.xt@hitachi.com

  reply	other threads:[~2011-08-27 12:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25  9:03 [-v3 PATCH 0/3] Persistent device name using alias Nao Nishijima
2011-08-25  9:04 ` [-v3 PATCH 1/3] block: add a new attribute "alias" in gendisk Nao Nishijima
2011-08-25  9:04 ` [-v3 PATCH 2/3] sd: [cleanup] Use sd_printk() instead of printk() Nao Nishijima
2011-08-25  9:04 ` [-v3 PATCH 3/3] sd: modify printk for alias name Nao Nishijima
2011-08-25 10:16 ` [-v3 PATCH 0/3] Persistent device name using alias Tejun Heo
2011-08-27 10:15   ` Nao Nishijima
2011-08-27 10:26     ` Tejun Heo
2011-08-27 12:54       ` Nao Nishijima [this message]
2011-08-27 13:20         ` Tejun Heo
2011-08-28 18:07           ` Kay Sievers
2011-08-30 21:53             ` Bernd Schubert
2011-08-30 20:02         ` Valdis.Kletnieks
2011-09-02 12:51           ` Nao Nishijima

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=4E58E905.4020704@hitachi.com \
    --to=nao.nishijima.xt@hitachi.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=axboe@kernel.dk \
    --cc=dle-develop@lists.sourceforge.net \
    --cc=kay.sievers@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=masami.hiramatsu.pt@hitachi.com \
    --cc=tj@kernel.org \
    --cc=yrl.pp-manager.tt@hitachi.com \
    /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