Re: PG's stuck inactive, stuck unclean, incomplete, imports cause osd segfaults

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 03/03/2016 07:21 PM, Philip S. Hempel wrote:

Philip,

Sorry, can't help you with the segfault. What i would do, is set debug options in ceph.conf and start the OSD, maybe that extra debug info will give something you can work with.



On 03/03/2016 01:15 PM, Richard Arends wrote:
On 03/03/2016 06:56 PM, Philip Hempel wrote:
I did the import after using the objectool to remove the pg and that osd (34) segfaults now.

Segfault output is not my cup of tea, but is that exact the same segfault as you posted earlier?


This is the full segfault

ceph version 0.94.5 (9764da52395923e0b32908d83a9f7304401fee43)
 1: /usr/bin/ceph-osd() [0xbf03dc]
 2: (()+0xf0a0) [0x7f5d35e5f0a0]
 3: (gsignal()+0x35) [0x7f5d347c9165]
 4: (abort()+0x180) [0x7f5d347cc3e0]
 5: (__gnu_cxx::__verbose_terminate_handler()+0x11d) [0x7f5d3501f89d]
 6: (()+0x63996) [0x7f5d3501d996]
 7: (()+0x639c3) [0x7f5d3501d9c3]
 8: (()+0x63bee) [0x7f5d3501dbee]
9: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x220) [0xcddda0]
 10: /usr/bin/ceph-osd() [0x7f578f]
11: (pg_interval_t::check_new_interval(int, int, std::vector<int, std::allocator<int> > const&, std::vector<int, std::allocator<int> > const&, int, int, std::vector <int, std::allocator<int> > const&, std::vector<int, std::allocator<int> > const&, unsigned int, unsigned int, std::tr1::shared_ptr<OSDMap const>, std::tr1::shared_p tr<OSDMap const>, pg_t, IsPGRecoverablePredicate*, std::map<unsigned int, pg_interval_t, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, pg_interval_t> > >*, std::ostream*)+0x2ba) [0x8c399a]
 12: (OSD::build_past_intervals_parallel()+0xbe1) [0x7d2261]
 13: (OSD::load_pgs()+0x2d8a) [0x7e977a]
 14: (OSD::init()+0xdac) [0x7ebb2c]
 15: (main()+0x253e) [0x78dd6e]
 16: (__libc_start_main()+0xfd) [0x7f5d347b5ead]
 17: /usr/bin/ceph-osd() [0x793de9]
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)
  -1/-1 (stderr threshold)
  max_recent     10000
  max_new         1000
  log_file /var/log/ceph/ceph-osd.34.log
--- end dump of recent events ---





--
Regards,

Richard.

_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com



[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux