Re: iozone test crashed on ceph

[udit agarwal <fzdudit@xxxxxxxxx>]

Hi,
 thanks for your reply.
 The output of 'modinfo ceph' is as follows:
 filename:       /lib/modules/3.1.10-1.9-desktop/kernel/fs/ceph/ceph.ko
license:        GPL
description:    Ceph filesystem for Linux
author:         Patience Warnick <patience@xxxxxxxxxxxx>
author:         Yehuda Sadeh <yehuda@xxxxxxxxxxxxxxx>
author:         Sage Weil <sage@xxxxxxxxxxxx>
srcversion:     AFEFF779535E750AFD4072D
depends:       
vermagic:       3.1.10-1.9-desktop SMP preempt mod_unload modversions

And my ceph.conf file is as follows:

[global]
   pid file = /var/run/ceph/$name.pid
   logger dir = /var/log/ceph
   log dir = /var/log/ceph
   user = root
[mon]
   mon data = /var/local/data/mon$id
;   debug ms = 1
;   debug mon = 20
;   debug paxos = 20
[mon.0]
   host = hp1
   mon addr = 192.168.20.6:6789
;[mon.1]
;   host = hp2
;   mon addr = 192.168.20.7:6789
;[mon.2]
;   host = bb1
;   mon addr = 192.168.20.2:6789
[mds]
;   debug ms = 1            ; message traffic
;   debug mds = 1           ; mds
;   debug mds balancer = 20 ; load balancing
;   debug mds log = 20      ; mds journaling
;   debug mds_migrator = 20 ; metadata migration
;   debug monc = 20         ; monitor interaction, startup
[mds.0]
   host = hp1
;[mds.1]
;   host = hp2
[osd]
   osd journal = /var/local/data/osd$id/journal
   osd journal size = 10000
   filestore journal writeahead = true
   osd data = /var/local/data/osd$id
;   debug ms = 1            ; message traffic
;   debug osd = 20
;   debug filestore = 20    ; local object storage
;   debug journal = 20      ; local journaling
;   debug monc = 20         ; monitor interaction, startup
[osd.0]
   host = el1
   btrfs devs = /dev/sda3
[osd.1]
   host = el1
   btrfs devs = /dev/sdb
[osd.2]
   host = bb1
   btrfs devs = /dev/sda3

No, I don't think so if any of them crashed.
Thanks in advance and let me know if you need further info.

--Udit

--
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