All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wido den Hollander <wido@42on.com>
To: Roman Alekseev <rs.alekseev@gmail.com>
Cc: Wolfgang Hennerbichler <wolfgang.hennerbichler@risc-software.at>,
	ceph-devel@vger.kernel.org
Subject: Re: rbd image association
Date: Mon, 03 Jun 2013 09:34:47 +0200	[thread overview]
Message-ID: <51AC4717.7010304@42on.com> (raw)
In-Reply-To: <51AC42FC.1040703@gmail.com>

On 06/03/2013 09:17 AM, Roman Alekseev wrote:
> On 03.06.2013 11:08, Wolfgang Hennerbichler wrote:
>> On Mon, Jun 03, 2013 at 10:52:14AM +0400, Roman Alekseev wrote:
>>> Hi,
>>>
>>> Is it possible to associate certain rbd device with the appropriate
>>> rbd image (for example : image1 > /dev/rbd0)?
>>> We always need to map image1 to /dev/rbd0, image2 to /dev/rbd1 etc.
>>> Because I'm using /dev/rbd* in some configuration files.
>> Hi,
>>
>> I can't remember exactly, but I think there is something like
>> /dev/rbd/<pool>/<imagename> which simply symlinks to /dev/rbdX. This
>> should solve your issue.
>>> Thanks
>> HTH
>> Wolfgang
>>
> Dear Wolfgang,
>
> I was trying to use the command ln -s /dev/rbd1 image1 but it creates
> wrong symlink. Most likely there is more specific command to symlink the
> image and device correctly.
>

Why are you symlinking? Like Wolfgang mentioned, udev takes care of this 
for you.

Just use /dev/rbd/pool/imagename which is created by udev.

> Thanks.
>


-- 
Wido den Hollander
42on B.V.

Phone: +31 (0)20 700 9902
Skype: contact42on

  reply	other threads:[~2013-06-03  7:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-03  6:52 rbd image association Roman Alekseev
     [not found] ` <20130603070836.GA2422@nix.wogri.at>
2013-06-03  7:17   ` Roman Alekseev
2013-06-03  7:34     ` Wido den Hollander [this message]
2013-06-03  7:45       ` Roman Alekseev
2013-06-03 14:49         ` Sage Weil
2013-06-03 14:54           ` Roman Alekseev
2013-06-03 14:56             ` Sage Weil
2013-06-03  7:36     ` Wolfgang Hennerbichler

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=51AC4717.7010304@42on.com \
    --to=wido@42on.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=rs.alekseev@gmail.com \
    --cc=wolfgang.hennerbichler@risc-software.at \
    /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.