From: Roman Alekseev <rs.alekseev@gmail.com>
To: Sage Weil <sage@inktank.com>
Cc: Wido den Hollander <wido@42on.com>,
Wolfgang Hennerbichler <wolfgang.hennerbichler@risc-software.at>,
ceph-devel@vger.kernel.org
Subject: Re: rbd image association
Date: Mon, 03 Jun 2013 18:54:19 +0400 [thread overview]
Message-ID: <51ACAE1B.3090803@gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1306030748240.18537@cobra.newdream.net>
On 03.06.2013 18:49, Sage Weil wrote:
> On Mon, 3 Jun 2013, Roman Alekseev wrote:
>> On 03.06.2013 11:34, Wido den Hollander wrote:
>>> udev takes car
>> Do you mean we need to create some rules in /etc/udev/rules.d/ directory and
>> after running rbd -p pool map image my image will be mapped with appropriate
>> device?
> The ceph package installs a udev rules file in that directory; you
> shouldn't have to do anything other than the 'rbd map ..' command. If it
> is not already present, there must be something wrong with the package on
> the platform you are using. What OS is it?
>
>> If so, could you please provide me with the commands which should be presented
>> in that file?
>>
>> Thanks
>>
>> --
>> Kind regards,
>>
>> R. Alekseev
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>>
>>
Yep, u're right there is only the file 70-persistent-net.rules in
/etc/udev/rules.d/ directory.
It is Debian Wheezy 3.2.0-4-amd64
thanks
--
Kind regards,
R. Alekseev
next prev parent reply other threads:[~2013-06-03 14:54 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
2013-06-03 7:45 ` Roman Alekseev
2013-06-03 14:49 ` Sage Weil
2013-06-03 14:54 ` Roman Alekseev [this message]
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=51ACAE1B.3090803@gmail.com \
--to=rs.alekseev@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=sage@inktank.com \
--cc=wido@42on.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.