I'm using head of line from the master branch. But that particular code hasn't changed since January, which is 0.24.2 is from. In my ceph.conf, I just had an osd that was on a remote machine, and everything else local. If you could post your ceph.conf here or in IRC, perhaps we might spot an issue that's causing the problems that you see. Colin On Wed, Feb 16, 2011 at 11:01 PM, Upendra Moturi <upendra.m@xxxxxxxxxxxx> wrote: > Hi Colin > I am using > ceph version 0.24.2 commit:f7572de5cb87eb7157217be4975ae66d90831bb7 > ubuntu 11.04 32 bit with upgraded kernal of 2.6.38-2-generic > > Installed ceph form apt source. > > With above configurations i still able yo reproduce. > Can you please share me ur configurations? > > On Thu, Feb 17, 2011 at 3:31 AM, Colin McCabe <cmccabe@xxxxxxxxxxxxxx> wrote: >> On Wed, Feb 16, 2011 at 1:41 PM, Colin McCabe <cmccabe@xxxxxxxxxxxxxx> wrote: >>> On Wed, Feb 16, 2011 at 6:44 AM, Upendra Moturi <upendra.m@xxxxxxxxxxxx> wrote: >>>> But if we want to start a particular osd or mon or mds ,its not >>>> working and there is no error >>>> eg:/etc/init.d/ceph start osd1 does not start osd1 and don't get any error >>> >>> That is expected, unless you are running init-ceph on the same node as >>> osd1 is on. >>> >>> It might be nice to have some kind of interface like "run command X on >>> osd1", but init-ceph is not that. >>> >>>> /etc/init.d/ceph -a stop also does not stop ceph on all nodes.It stops >>>> on current node only >>>> where as >>>> /etc/init.d/ceph -a killall works fine. >>> >>> That sounds like a bug. I'll see if I can fix it. >> >> I'm afraid I can't reproduce this. >> >> I ran /etc/init.d/ceph -a stop >> >> and it stopped ceph daemons running on remote nodes too. Looking at >> the code, it looks correct. >> >> Colin >> > > > > -- > Thanks and Regards, > Upendra.M > -- 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
