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. 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. ��.n��������+%������w��{.n����z��u���ܨ}���Ơz�j:+v�����w����ޙ��&�)ߡ�a����z�ޗ���ݢj��w�f
