When I create a new OSD with a block device as journal that has existing data on it, ceph is causing FAILED assert. The block device iss a journal from a previous experiment. It can safely be overwritten. If I zero the block device with dd if=/dev/zero bs=512 count=1000 of=MyJournalDev then the assert doesn't happen. Is there a way to tell mkfs to ignore data on the journal device and just go ahead and clobber it ? 2014-11-13 21:22:26.463359 7f8383486880 -1 journal Unable to read past sequence 2 but header indicates the journal has committed up through 5202, journal is cor rupt os/FileJournal.cc: In function 'bool FileJournal::read_entry(ceph::bufferlist&, uint64_t&, bool*)' thread 7f8383486880 time 2014-11-13 21:22:26.463363 os/FileJournal.cc: 1693: FAILED assert(0) ceph version 0.87 (c51c8f9d80fa4e0168aa52685b8de40e42758578) 1: (ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x85) [0xb7ac55] 2: (FileJournal::read_entry(ceph::buffer::list&, unsigned long&, bool*)+0xb04) [0xa339a4] 3: (JournalingObjectStore::journal_replay(unsigned long)+0x237) [0x910787] 4: (FileStore::mount()+0x3f8b) [0x8e482b] 5: (OSD::mkfs(CephContext*, ObjectStore*, std::string const&, uuid_d, int)+0xf0) [0x65d940] 6: (main()+0xbf6) [0x620d76] 7: (__libc_start_main()+0xf5) [0x7f8380823af5] 8: ceph-osd() [0x63a969] NOTE: a copy of the executable, or `objdump -rdS <executable>` is needed to interpret this. _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
 |