On 6/13/17 2:46 PM, Yan, Zheng wrote:
> On Mon, Jun 12, 2017 at 10:45 PM, Georgi Chorbadzhiyski <gf@xxxxxxxxxxx> wrote:
>> On 6/12/17 3:58 PM, Yan, Zheng wrote:
>>> On Mon, Jun 12, 2017 at 6:56 PM, Georgi Chorbadzhiyski <gf@xxxxxxxxxxx> wrote:
>>>> On 6/12/17 1:22 PM, John Spray wrote:
>>>>> On Mon, Jun 12, 2017 at 5:13 AM, Georgi Chorbadzhiyski <gf@xxxxxxxxxxx> wrote:
>>>>>> We started getting these on all of our 3 MDS-es. Any idea how to fix it or at least debug
>>>>>> it and remove the dir entries that are causing the problem?
>>>>>
>>>>> Assuming it's easy to reproduce, set "debug mds = 20", "debug ms = 1"
>>>>> and gather the logs in the run up to the crash.
>>>>
>>>> After turning up debug as you suggested here are the logs before the crash.
>>>>
>>>> -10> 2017-06-12 05:46:05.808399 7fc8038d2700 10 MDSInternalContextBase::complete: 18C_MDS_RetryRequest
>>>> -9> 2017-06-12 05:46:05.808401 7fc8038d2700 7 mds.0.server dispatch_client_request client_request(client.467465:121280822 readdir #1000007d3e8 sess_umos5jqii50rttcag852lros73 2017-06-12 03:36:19.073284 RETRY=115 caller_uid=1838, caller_gid=1838{}) v2
>>>> -8> 2017-06-12 05:46:05.808407 7fc8038d2700 10 mds.0.server rdlock_path_pin_ref request(client.467465:121280822 cr=0x7fc819988f00) #1000007d3e8
>>>> -7> 2017-06-12 05:46:05.808410 7fc8038d2700 10 mds.0.locker acquire_locks request(client.467465:121280822 cr=0x7fc819988f00) - done locking
>>>> -6> 2017-06-12 05:46:05.808416 7fc8038d2700 20 Session check_access path /client/shared/site.com/oc-content/uploads/session
>>>> -5> 2017-06-12 05:46:05.808418 7fc8038d2700 10 MDSAuthCap is_capable inode(path /client/shared/site.com/oc-content/uploads/session owner 1838:1838 mode 040755) by caller 1838:1838 mask 1 new 1024:524288 cap: MDSAuthCaps[allow *]
>>>>
>>>> -4> 2017-06-12 05:46:05.808423 7fc8038d2700 10 mds.0.server frag 1* offset 'sess_umos5jqii50rttcag852lros73' offset_hash 13141348 flags 0
>>>> -3> 2017-06-12 05:46:05.808426 7fc8038d2700 10 mds.0.server adjust frag 1* -> 1000* fragtree_t(*^1 0*^1 1*^3)
>>>> -2> 2017-06-12 05:46:05.808430 7fc8038d2700 10 mds.0.server handle_client_readdir on [dir 1000007d3e8.1000* /client/shared/site.com/oc-content/uploads/session/ [2,head] auth pv=1077482 v=1077481 cv=0/0 ap=1+2+2 state=1610612738|complete f(v86 218=218+0) n(v10 b67671 218=218+0) hs=218+6,ss=0+0 dirty=10 | child=1 dirty=1 waiter=0 authpin=1 0x7fc828eae340]
>>>> -1> 2017-06-12 05:46:05.808447 7fc8038d2700 10 mds.0.server snapid head
>>>> 0> 2017-06-12 05:46:05.843735 7fc8038d2700 -1 *** Caught signal (Segmentation fault) **
>>>> in thread 7fc8038d2700 thread_name:ms_dispatch
>>>
>>> The log doesn't contain useful information for this issue. Could you
>>> please enable coredump try again. Besides, please install debug info
>>> for ceph-mds or re-compile ceph with debug info. After got coredump,
>>> using gdb to debug this issue is convenient.
>>
>> I have core dump, where can I get the debug info for official centos 7
>> packages?
>
> I don't use centos. I found link
> https://wiki.centos.org/AdditionalResources/Repositories/DebugInfo
I already have this :) I needed ceph binaries with debug info, not the generic
ones.
--
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
