All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@dreamhost.com>
To: Eric_YH_Chen@wistron.com
Cc: tommi.virtanen@dreamhost.com, ceph-devel@vger.kernel.org,
	Chris_YT_Huang@wistron.com
Subject: Re: rbd device would disappear after re-boot
Date: Thu, 08 Dec 2011 16:58:21 -0800	[thread overview]
Message-ID: <4EE15D2D.8070204@dreamhost.com> (raw)
In-Reply-To: <8512670932FB654F81AF0FEF1BE6D49D943CC9@WHQBEMAIL1.whq.wistron>

On 12/07/2011 11:31 PM, Eric_YH_Chen@wistron.com wrote:
> Hi, Tommi:
>
> What I see is like this.
>
> lrwxrwxrwx 1 root root 10 2011-12-07 16:48 foo1:0 ->  ../../rbd0
> lrwxrwxrwx 1 root root 10 2011-12-07 16:50 foo2:1 ->  ../../rbd1
>
> The extra number (:0 and :1) behind the image name make the problem still exists.

I'm not sure why we had the device number in the udev rule. I removed it 
in 891025e539a92b5d75011e2e75c475fc0c272042.

>
> -----Original Message-----
> From: Tommi Virtanen [mailto:tommi.virtanen@dreamhost.com]
> Sent: Thursday, December 08, 2011 1:31 AM
> To: Eric YH Chen/WHQ/Wistron
> Cc: ceph-devel@vger.kernel.org; Chris YT Huang/WHQ/Wistron
> Subject: Re: rbd device would disappear after re-boot
>
> On Tue, Dec 6, 2011 at 18:38,<Eric_YH_Chen@wistron.com>  wrote:
>> I have another little question. Could I map specific image to specific device?
>>
>> For example:
>> Before re-boot
>> id      pool    image   snap    device
>> 0       rbd     foo1    -       /dev/rbd0
>> 1       rbd     foo3    -       /dev/rbd2
>>
>> How could I re-map the image(foo3) to device(/dev/rbd2) but skip rbd1?  The command provided by ceph CLI cannot achieve this.
>>
>> If I re-map the image to another device, it would not sync with iSCSI configuration and may cause problem.
>
> I'm just confirming what Damien said. Don't rely on the numbering to
> be consistent even from one boot to another; we provide a udev helper
> that assigns more permanent names, based on the pool, image name, and
> potentially snapshot name. You'll get a symlink like
> /dev/rbd/POOL/IMAGE or /dev/rbd/POOL/IMAGE@SNAP, use that name.

      reply	other threads:[~2011-12-09  0:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-06  9:31 rbd device would disappear after re-boot Eric_YH_Chen
2011-12-06 19:10 ` Tommi Virtanen
2011-12-07  2:38   ` Eric_YH_Chen
2011-12-07  2:48     ` Damien Churchill
2011-12-07 17:31     ` Tommi Virtanen
2011-12-08  7:31       ` Eric_YH_Chen
2011-12-09  0:58         ` Josh Durgin [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=4EE15D2D.8070204@dreamhost.com \
    --to=josh.durgin@dreamhost.com \
    --cc=Chris_YT_Huang@wistron.com \
    --cc=Eric_YH_Chen@wistron.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=tommi.virtanen@dreamhost.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.