On Wed, Dec 1, 2010 at 5:38 PM, Jeff Wu <cpwu@xxxxxxxxxxxxx> wrote: >> > and i also detect a issue ,take the following steps: >> > >> > $. mckephfs -c ceph.conf -v --mkbtrfs -a >> > $ init-ceph - ceph.conf --btrfs -v -a start >> > then execute: >> > $ init-ceph - ceph.conf --btrfs -v -a stop >> > >> > this command can't stop OSD0 and OSD1 cosd process: >> > OSD0: >> > /usr/local/bin/cosd -i 0 -c ceph.conf >> > OSD1: >> > /usr/local/bin/cosd -i 1 -c ceph.conf >> Not sure I understand what you're doing here. Also, it looks like >> you've got a malformed command there -- you don't specify the "-c" >> option, just the nonexistent "-" option. ;) > > Oh,Sorry, i mean that , if i don't create folder "/var/run/ceph" at OSD > hosts manually. Execute the command : "$init-ceph -c ceph.conf --btrfs > -v -a stop " ,which can't auto-kill OSD host cosd process, like this : > OSD0 host: > $ ps -ef | grep cosd > root 13987 1 0 Dec01 ? 00:02:55 /usr/local/bin/cosd -i 0 > -c ceph.conf > OSD1 host: > $ ps -ef | grep cosd > root 14028 1 0 Dec01 ? 00:02:53 /usr/local/bin/cosd -i 1 > -c ceph.conf > > I have to execute "kill -9 13987 " and "kill -9 14028" to kill cosd > process manually, or ,next time , it will fail to execute "$ init-ceph > -c ceph.conf --btrfs -v -a start " command. Ah. I think that /var/run/ceph is where init-ceph stores the PIDs. It ought to be created automatically; if it's not we should fix that. What version of Ceph are you running, and where from? I'd imagine it's being packaged wrong or something. -- 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
