public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nao Nishijima <nao.nishijima.xt@hitachi.com>
To: Valdis.Kletnieks@vt.edu
Cc: Tejun Heo <tj@kernel.org>,
	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: Fri, 02 Sep 2011 21:51:54 +0900	[thread overview]
Message-ID: <4E60D16A.8060802@hitachi.com> (raw)
In-Reply-To: <16628.1314734537@turing-police.cc.vt.edu>

Hi Valdis,

(2011/08/31 5:02), Valdis.Kletnieks@vt.edu wrote:
> On Sat, 27 Aug 2011 21:54:29 +0900, Nao Nishijima said:
> 
>> 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.
> 
> If this is important to you, can't you use a udev rule, similar to what most
> distros already stick in 70-persistent-net.rules and 70-persistent-cd.rules?
> 
> (Yes, this *does* involve finding a UUID or label or  something on the disk
> that you can identify as "same entity as last time".

As you said, it is able to identify a disk at the expense of checking
cost. However to introduce "alias" is an advantage of reducing both the
cost and the risk of miss-communication, and it can easily identify it.

And also, currently, kernel log and command output do not accord with
the device name which a user uses (e.g. by-id, by-uuid). I would try to
solve those mismatches using "alias". In other words, I'd like to
introduce aliases for integrating the name of devices to control and record.

Of course I will modify commands using a device name to use a persistent
device names.


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-09-02 12:52 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
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 [this message]

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=4E60D16A.8060802@hitachi.com \
    --to=nao.nishijima.xt@hitachi.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Valdis.Kletnieks@vt.edu \
    --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