Re: rbd device would disappear after re-boot

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 7 December 2011 02:38,  <Eric_YH_Chen@xxxxxxxxxxx> wrote:
> Hi, Tommi:
>
> Thanks for your suggestion.
>
> We will try to implement a workaround solution for our internal experiment.
>
> 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.
>

You can use the symlinks created, if memory serves they end up as
something along the lines of:

/dev/rbd/<poolname>/<diskname>:0

> Thanks a lot!
>
>
> -----Original Message-----
> From: Tommi Virtanen [mailto:tommi.virtanen@xxxxxxxxxxxxx]
> Sent: Wednesday, December 07, 2011 3:11 AM
> To: Eric YH Chen/WHQ/Wistron
> Cc: ceph-devel@xxxxxxxxxxxxxxx; Chris YT Huang/WHQ/Wistron
> Subject: Re: rbd device would disappear after re-boot
>
> On Tue, Dec 6, 2011 at 01:31,  <Eric_YH_Chen@xxxxxxxxxxx> wrote:
>>   Another question about the rbd device. All rbd device would disappear
>> after server re-boot.
>>
>>   Do you have any plan to implement a feature that server would re-map
>> all the device during initialization?
>>
>>   If not, do you have any suggestion (about technical part) if we want
>> to implement this feature?
>>
>>   Furthermore, we would like to send a pull request after we finish it,
>> any policy should we take-care?
>
> Yes, all mappings need to be re-established after a reboot.
>
> There is no convention yet on configuring what should be
> re-established. Right now, putting an "rbd map" in something like
> /etc/rc.local is a decent workaround.
>
> I created http://tracker.newdream.net/issues/1790 to track this feature.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux