Hello Sage, Just opened the bug. here is the link http://tracker.newdream.net/issues/3663 thanks! 2012/12/20 Sam Lang <sam.lang@xxxxxxxxxxx>: > On 12/19/2012 10:02 PM, Roman Hlynovskiy wrote: >> >> Hello Sage, >> >> Yes, I can easily reproduce it. >> >> how can I open a bug on the tracker? I can't find the link for this. >> log is ready to be uploaded. > > > Hi Roman, > > The bug tracker is at: http://tracker.newdream.net/ > > Once you've created an account, you can jump to the project 'fs' through the > scroll down bar on the right, and then click on the 'New Issue' tab. > > -sam > > >> this is pure kernel client mount. my kernel on the client is >> 3.2.0-0.bpo.3-686-pae >> >> 2012/12/19 Sage Weil <sage@xxxxxxxxxxx>: >>> >>> On Wed, 19 Dec 2012, Roman Hlynovskiy wrote: >>>> >>>> My second problem - I have 2 systems which mount ceph. Whenever I >>>> mount ceph on any other system it usually mounts but get stuck on >>>> stat* operations (i.e. simple ls -al will hang with read( from the >>>> ceph-mounted directory for ages). This kind of client stuck also >>>> affects two working clients. they also start to stuck on the stat* >>>> even after shutdown of the third client. so usually umount/mount or >>>> even reboot for existing clients solves the issue) >>> >>> >>> If this is something you can easily reproduce, can you please run with >>> >>> [mds] >>> debug mds = 20 >>> debug ms = 1 >>> >>> in your ceph.conf and attach the resulting mds log to a bug in the >>> tracker? We've seen this sort of thing in the past, but not recently. >>> >>> Is this the kernel client mount? What version of the client (kernel) are >>> you running? >>> >>> Thanks! >>> sage >>> >>> >>> >> >> >> > -- ...WBR, Roman Hlynovskiy -- 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
