When you do:
$ rbd create
You are using the kernel (i.e 3.13) code for rbd, and this is likely
much older than the code you just built for the rest of Ceph. You
*might* have better luck installing the vivid kernel (3.19) on your
trusty system are trying again.
Having said that - seg fault is pretty evil, should really fail in a
nicer way if the kernel client is too old to work with the newer
Ceph...I'd raise an issue anyway and see what the devs say!
Regards
Mark
On 13/11/15 15:17, Artie Ziff wrote:
When I run `rbd create` => seg fault
It worked on previous pulls/builds.
I would need to regress/rebuild to provide version info that worked last.
Ubuntu 14.04.3 LTS
Linux ceph-mon-node 3.13.0-65-generic #106-Ubuntu SMP / x86_64 x86_64
x86_64 GNU/Linux
configure --prefix=/usr/local --sysconfdir=/etc
For those with much more experience with this code base...
Is this likely my configuration problem or should it not happen ever and
needs a bug filed?
Thx!
az
####
rbd create im1 --size 35840 -p pool1
*** Caught signal (Segmentation fault) **
in thread 7f1db4ea07c0
ceph version 0.94.5 (9764da52395923e0b32908d83a9f7304401fee43)
1: rbd() [0x5a71ea]
2: (()+0x10340) [0x7f1db3035340]
3: (ceph::crypto::init(CephContext*)+0x1b) [0x7f1db36ce7db]
4: (common_init_finish(CephContext*, int)+0x10) [0x7f1db36a1a30]
5: (librados::RadosClient::connect()+0x1f) [0x7f1db35e957f]
6: (main()+0x2952) [0x4cd632]
7: (__libc_start_main()+0xf5) [0x7f1db1785ec5]
8: rbd() [0x4d3457]
2015-11-12 17:55:07.735813 7f1db4ea07c0 -1 *** Caught signal
(Segmentation fault) **
in thread 7f1db4ea07c0
ceph version 0.94.5 (9764da52395923e0b32908d83a9f7304401fee43)
1: rbd() [0x5a71ea]
2: (()+0x10340) [0x7f1db3035340]
3: (ceph::crypto::init(CephContext*)+0x1b) [0x7f1db36ce7db]
4: (common_init_finish(CephContext*, int)+0x10) [0x7f1db36a1a30]
5: (librados::RadosClient::connect()+0x1f) [0x7f1db35e957f]
6: (main()+0x2952) [0x4cd632]
7: (__libc_start_main()+0xf5) [0x7f1db1785ec5]
8: rbd() [0x4d3457]
NOTE: a copy of the executable, or `objdump -rdS <executable>` is
needed to interpret this.
--- begin dump of recent events ---
-14> 2015-11-12 17:55:07.731825 7f1db4ea07c0 5 asok(0x32c5df0)
register_command perfcounters_dump hook 0x32c9580
-13> 2015-11-12 17:55:07.731849 7f1db4ea07c0 5 asok(0x32c5df0)
register_command 1 hook 0x32c9580
-12> 2015-11-12 17:55:07.731852 7f1db4ea07c0 5 asok(0x32c5df0)
register_command perf dump hook 0x32c9580
-11> 2015-11-12 17:55:07.731862 7f1db4ea07c0 5 asok(0x32c5df0)
register_command perfcounters_schema hook 0x32c9580
-10> 2015-11-12 17:55:07.731864 7f1db4ea07c0 5 asok(0x32c5df0)
register_command 2 hook 0x32c9580
-9> 2015-11-12 17:55:07.731874 7f1db4ea07c0 5 asok(0x32c5df0)
register_command perf schema hook 0x32c9580
-8> 2015-11-12 17:55:07.731876 7f1db4ea07c0 5 asok(0x32c5df0)
register_command perf reset hook 0x32c9580
-7> 2015-11-12 17:55:07.731884 7f1db4ea07c0 5 asok(0x32c5df0)
register_command config show hook 0x32c9580
-6> 2015-11-12 17:55:07.731886 7f1db4ea07c0 5 asok(0x32c5df0)
register_command config set hook 0x32c9580
-5> 2015-11-12 17:55:07.731888 7f1db4ea07c0 5 asok(0x32c5df0)
register_command config get hook 0x32c9580
-4> 2015-11-12 17:55:07.731895 7f1db4ea07c0 5 asok(0x32c5df0)
register_command config diff hook 0x32c9580
-3> 2015-11-12 17:55:07.731896 7f1db4ea07c0 5 asok(0x32c5df0)
register_command log flush hook 0x32c9580
-2> 2015-11-12 17:55:07.731899 7f1db4ea07c0 5 asok(0x32c5df0)
register_command log dump hook 0x32c9580
-1> 2015-11-12 17:55:07.731906 7f1db4ea07c0 5 asok(0x32c5df0)
register_command log reopen hook 0x32c9580
0> 2015-11-12 17:55:07.735813 7f1db4ea07c0 -1 *** Caught signal
(Segmentation fault) **
in thread 7f1db4ea07c0
ceph version 0.94.5 (9764da52395923e0b32908d83a9f7304401fee43)
1: rbd() [0x5a71ea]
2: (()+0x10340) [0x7f1db3035340]
3: (ceph::crypto::init(CephContext*)+0x1b) [0x7f1db36ce7db]
4: (common_init_finish(CephContext*, int)+0x10) [0x7f1db36a1a30]
5: (librados::RadosClient::connect()+0x1f) [0x7f1db35e957f]
6: (main()+0x2952) [0x4cd632]
7: (__libc_start_main()+0xf5) [0x7f1db1785ec5]
8: rbd() [0x4d3457]
NOTE: a copy of the executable, or `objdump -rdS <executable>` is
needed to interpret this.
--- logging levels ---
0/ 5 none
0/ 1 lockdep
0/ 1 context
1/ 1 crush
1/ 5 mds
1/ 5 mds_balancer
1/ 5 mds_locker
1/ 5 mds_log
1/ 5 mds_log_expire
1/ 5 mds_migrator
0/ 1 buffer
0/ 1 timer
0/ 1 filer
0/ 1 striper
0/ 1 objecter
0/ 5 rados
0/ 5 rbd
0/ 5 rbd_replay
0/ 5 journaler
0/ 5 objectcacher
0/ 5 client
0/ 5 osd
0/ 5 optracker
0/ 5 objclass
1/ 3 filestore
1/ 3 keyvaluestore
1/ 3 journal
0/ 5 ms
1/ 5 mon
0/10 monc
1/ 5 paxos
0/ 5 tp
1/ 5 auth
1/ 5 crypto
1/ 1 finisher
1/ 5 heartbeatmap
1/ 5 perfcounter
1/ 5 rgw
1/10 civetweb
1/ 5 javaclient
1/ 5 asok
1/ 1 throttle
0/ 0 refs
1/ 5 xio
-2/-2 (syslog threshold)
99/99 (stderr threshold)
max_recent 500
max_new 1000
log_file
--- end dump of recent events ---
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
