hi, is there any way to debug ceph to find out where it crash? Thanks, Sheng On Mon, Oct 24, 2011 at 11:55 AM, Tommi Virtanen <tommi.virtanen@xxxxxxxxxxxxx> wrote: > On Sun, Oct 23, 2011 at 12:22, sheng qiu <herbert1984106@xxxxxxxxx> wrote: >> does ceph only support ext3 and btrfs? i mean if i have another file >> system, it support xattr, but it does not support journals, can i >> close the journal config and run it with ceph? > > Ceph supports OSD storage on POSIX-compliant filesystems with extended > attributes. There are some edge cases that are still problematic, see > the email with subject "ceph on non-btrfs file systems" that Sage just > sent for a better discussion of those. > > I'm not sure what you mean by a filesystem "not supporting journals", > the ceph-osd journal is just a file it writes to. I'm not sure what > you mean by "closing the journal config"; you can disable the journal, > but that will likely just make things slower; once again, using a > journal is possible on any filesystem, btrfs just makes it more > effective. > >> i tried to do that by modifying the ceph.conf file (close the journal >> on osd). the mkcephfs seems ok, but when i start the service, cosd >> will crash. >> here's the log: >> *** Caught signal (Aborted) ** >> in thread 0x7f1845ce6720 >> ceph version 0.34 (commit:2f039eeeb745622b866d80feda7afa055e15f6d6) >> 1: ./cosd() [0x5c6304] > ... >> 9: (CrushWrapper::decode(ceph::buffer::list::iterator&)+0xac) [0x5611fc] >> 10: (OSDMap::decode(ceph::buffer::list&)+0x8aa) [0x5622aa] >> 11: (OSD::get_map(unsigned int)+0x221) [0x52f441] > > That sounds more like the osdmap is corrupt, somehow. Anyone else have > more specific suggestions? > -- Sheng Qiu Texas A & M University Room 302 Wisenbaker email: herbert1984106@xxxxxxxxx College Station, TX 77843-3259 -- 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
