Actions
Bug #4487
closedosd: FAILED assert(0 == "FileJournal::read_entry(): corrupt journal")
% Done:
0%
Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
While attempting to trigger a monitor bug, triggered this instead.
Unfortunately, both the machine state and the osd logs were lost as I assumed I had finally triggered said monitor bug.
Triggered once in 55 runs using the following job yaml. Also, attaching teuthology log as that's the only thing (aside from the mon logs) that has survived.
interactive-on-error: true overrides: ceph: conf: global: ms inject delay max: 1 ms inject delay probability: 0.005 ms inject delay type: osd ms inject socket failures: 2500 mon: debug ms: 1 debug mon: 20 fs: xfs log-whitelist: - slow request branch: wip-pglog roles: - - mon.a - mon.b - osd.0 - osd.1 - osd.2 - - mon.c - mds.a - osd.3 - osd.4 - osd.5 - client.0 tasks: - chef: null - clock: null - install: - ceph: log-whitelist: - wrongly marked me down - objects unfound and apparently lost - thrashosds: timeout: 1200 - rados: clients: - client.0 objects: 500 op_weights: delete: 50 read: 100 rollback: 50 snap_create: 50 snap_remove: 50 write: 100 ops: 4000
Files
Updated by Ian Colle about 11 years ago
- Assignee set to Samuel Just
- Priority changed from Normal to Urgent
Actions