Project

General

Profile

Actions
Copy link

Bug #4729

closed

mds: stuck in clientreplay

Added by Sage Weil about 11 years ago. Updated almost 8 years ago.

Status:
Can't reproduce
Priority:
Urgent
Assignee:
-
Category:
-
Target version:
-
% Done:

0%

Source:
Q/A
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
MDS
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

job was

ubuntu@teuthology:/var/lib/teuthworker/archive/teuthology-2013-04-15_01:00:42-fs-master-testing-basic/13023$ cat orig.config.yaml 
kernel:
  kdb: true
  sha1: 6879b7f042355cd8b864802947824d8bb57517c8
nuke-on-error: true
overrides:
  ceph:
    log-whitelist:
    - slow request
    - wrongly marked me down
    sha1: 06a95a6e3856c6c919bc9e3ff9f49b1ac661492d
  s3tests:
    branch: master
  workunit:
    sha1: 06a95a6e3856c6c919bc9e3ff9f49b1ac661492d
roles:
- - mon.a
  - mon.c
  - osd.0
  - osd.1
  - osd.2
- - mon.b
  - mds.a
  - osd.3
  - osd.4
  - osd.5
- - client.0
  - mds.b-s-a
tasks:
- chef: null
- clock: null
- install: null
- ceph: null
- mds_thrash: null
- ceph-fuse: null
- workunit:
    clients:
      all:
      - suites/pjd.sh

Actions
Copy link
 #1

Updated by Greg Farnum about 11 years ago

  • Status changed from New to Can't reproduce

Unfortunately by the time I got in one of the machines had been allocated for another job, and now it looks like the second one has been as well; nor was there any logging available.
My hope is that this was actually a symptom of network issues as with the other hung mds thrasher things we've seen lately, but if not we will presumably see it again.

Actions
Copy link
 #2

Updated by Greg Farnum almost 8 years ago

  • Component(FS) MDS added
Actions
Copy link

Also available in: Atom PDF