å 2010-12-02åç 00:05 +0800ïGregory Farnumåéï > On Tue, Nov 30, 2010 at 10:57 PM, Jeff Wu <cpwu@xxxxxxxxxxxxx> wrote: > > Hi ,greg, > > > > With your suggestions, i add the journal config: > > " > > osd data = /opt/ceph/data/osd$id > > osd journal = /home/transoft/data/osd$id/journal > > filestore journal writeahead = true > > osd journal size = 10000 > > " > > to ceph.conf. the detail ceph.conf attached below. > > > > then , run six times for the commad: "$ sudo ceph osd tell 0/1 bench" ,get > > the results: > > > > > > $ sudo ceph -w > > > > osd0 172.16.10.42:6800/17347 1 : [INF] bench: wrote 1024 MB in blocks of > > 4096 KB in 29.818194 sec at 28201 KB/sec > > osd0 172.16.10.42:6800/17347 2 : [INF] bench: wrote 1024 MB in blocks of > > 4096 KB in 30.013058 sec at 34801 KB/sec > > osd0 172.16.10.42:6800/17347 3 : [INF] bench: wrote 1024 MB in blocks of > > 4096 KB in 30.463511 sec at 30274 KB/sec > > > > osd1 172.16.10.65:6800/4845 1 : [INF] bench: wrote 1024 MB in blocks of 4096 > > KB in 165.067603 sec at 6329 KB/sec > > osd1 172.16.10.65:6800/4845 2 : [INF] bench: wrote 1024 MB in blocks of 4096 > > KB in 181.034333 sec at 5782 KB/sec > > osd1 172.16.10.65:6800/4845 3 : [INF] bench: wrote 1024 MB in blocks of 4096 > > KB in 196.055812 sec at 5334 KB/sec > > > > and i also use "dd" to test raw drive, get the logs: > > > > 1. OSD0, mkfs.btrfs format /opt > > > > $ sudo dd if=/dev/zero of=/opt/dd.img bs=2M count=1024 > > 1024+0 records in > > 1024+0 records out > > 2147483648 bytes transfered in 21.4497 secs(100 MB/sec) > > > > 2. OSD1 ,mkfs. btrfs format /opt > > > > ~$ sudo dd if=/dev/zero of=/opt/dd.img bs=2M count=1024 > > 1024+0 records in > > 1024+0 records out > > 2147483648 bytes transfered in 48.2037 secs(44.6 MB/sec) > > > > with these logs, OSD1 disk speed might limit the test performance. > Yes, it looks to me like your OSD1 disk isn't working properly. > Switching it from one streaming write to two streaming writes > shouldn't reduce it to 20% of its original performance (~45MB/s to > 5MB/s*2). The same change in tasks doesn't impact OSD0's disk at all. > Hi greg, thank you for your detail comments. > > 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. jeff,wu -- 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
