Bug 1593093 - [CephFS][CodeChange] mds: scrub stuck at trimming log segments
Summary: [CephFS][CodeChange] mds: scrub stuck at trimming log segments
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat
Component: CephFS
Version: 3.0
Hardware: All
OS: All
Target Milestone: z5
: 3.0
Assignee: Patrick Donnelly
QA Contact: ceph-qe-bugs
Depends On:
TreeView+ depends on / blocked
Reported: 2018-06-20 03:24 UTC by Yan, Zheng
Modified: 2018-08-09 18:27 UTC (History)
4 users (show)

Fixed In Version: RHEL: ceph-12.2.4-32 Ubuntu: ceph_12.2.4-36redhat1xenial
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2018-08-09 18:27:11 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Ceph Project Bug Tracker 23930 None None None 2018-06-20 16:39:11 UTC
Red Hat Product Errata RHBA-2018:2375 None None None 2018-08-09 18:27:42 UTC

Description Yan, Zheng 2018-06-20 03:24:24 UTC
Description of problem:

The scrub code calls MDLog::trim_all() without flushing mdlog first. when there is no expiring log segment, MDSGatherBuilder malfunction. (MDSGatherBuilder::activate() does not execute empty MDSGatherBuilder's finish context)

Comment 3 Yan, Zheng 2018-06-20 07:29:23 UTC
zhyan-laptop:ceph zhyan$ git push rh-ceph ceph-3.0-rhel-patches 
Counting objects: 62, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (57/57), done.
Writing objects: 100% (62/62), 11.35 KiB | 726.00 KiB/s, done.
Total 62 (delta 54), reused 5 (delta 5)
remote: Resolving deltas: 100% (54/54)
remote: Processing changes: refs: 1, done    
To ssh://code.engineering.redhat.com/ceph/.git
   0b3592f04c..1e9171374c  ceph-3.0-rhel-patches -> ceph-3.0-rhel-patches

Comment 14 errata-xmlrpc 2018-08-09 18:27:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.