On Wed, 26 Oct 2011, sheng qiu wrote: > thanks for the reply. i met a new problem. now i can mount the ceph > using cfuse. and write small single file. but it will crash when file > size increased to some number. the osd.log is: > 2011-10-26 08:59:20.156983 7febdca06700 journal FileJournal::write_bl > : write_fd failed: error 13: Permission denied We're getting an error when trying to write to the journal device. Is that a file or a block device? I'm not sure what would cause a write EACCES on an already-open file... And strace -f log might on the ceph-osd might tell us more. sage > 2011-10-26 08:59:20.157000 7febdca06700 journal FileJournal::do_write: > write_bl(pos=10481664) failed > os/FileJournal.cc: In function 'void > FileJournal::do_write(ceph::bufferlist&)', in thread '0x7febdca06700' > os/FileJournal.cc: 817: FAILED assert(0) > ceph version 0.34 (commit:2f039eeeb745622b866d80feda7afa055e15f6d6) > 1: (FileJournal::do_write(ceph::buffer::list&)+0x367) [0x6b61f7] > 2: (FileJournal::write_thread_entry()+0x3e6) [0x6b97c6] > 3: (FileJournal::Writer::entry()+0xd) [0x6a50dd] > 4: (()+0x69ca) [0x7febe38119ca] > 5: (clone()+0x6d) [0x7febe22f870d] > ceph version 0.34 (commit:2f039eeeb745622b866d80feda7afa055e15f6d6) > 1: (FileJournal::do_write(ceph::buffer::list&)+0x367) [0x6b61f7] > 2: (FileJournal::write_thread_entry()+0x3e6) [0x6b97c6] > 3: (FileJournal::Writer::entry()+0xd) [0x6a50dd] > 4: (()+0x69ca) [0x7febe38119ca] > 5: (clone()+0x6d) [0x7febe22f870d] > *** Caught signal (Aborted) ** > in thread 0x7febdca06700 > ceph version 0.34 (commit:2f039eeeb745622b866d80feda7afa055e15f6d6) > 1: ./cosd() [0x5c69d4] > 2: (()+0xf8f0) [0x7febe381a8f0] > 3: (gsignal()+0x35) [0x7febe2245a75] > 4: (abort()+0x180) [0x7febe22495c0] > 5: (__gnu_cxx::__verbose_terminate_handler()+0x115) [0x7febe2afb8e5] > 6: (()+0xcad16) [0x7febe2af9d16] > 7: (()+0xcad43) [0x7febe2af9d43] > 8: (()+0xcae3e) [0x7febe2af9e3e] > 9: (ceph::__ceph_assert_fail(char const*, char const*, int, char > const*)+0x39f) [0x5cbb1f] > 10: (FileJournal::do_write(ceph::buffer::list&)+0x367) [0x6b61f7] > 11: (FileJournal::write_thread_entry()+0x3e6) [0x6b97c6] > 12: (FileJournal::Writer::entry()+0xd) [0x6a50dd] > 13: (()+0x69ca) [0x7febe38119ca] > 14: (clone()+0x6d) [0x7febe22f870d] > > does any one have idea about this? > > Thanks, > Sheng > > On Mon, Oct 24, 2011 at 2:02 PM, sheng qiu <herbert1984106@xxxxxxxxx> wrote: > > 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 > > > > > > -- > 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 > >
