Actions
Bug #15921
closedsegfault in cephfs-journal-tool (TestJournalRepair failure)
Status:
Can't reproduce
Priority:
Normal
Assignee:
-
Category:
fsck/damage handling
Target version:
-
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
Seen on testing branch, but don't have any candidate causes in the things I was testing.
Updated by John Spray almost 8 years ago
- Priority changed from Normal to High
Updated by Greg Farnum almost 8 years ago
- Priority changed from High to Normal
As far as I can tell, we don't even have the backtrace of the segfault in either of those logs, and the sha1 isn't available so we can't get a build and compare the core dump we do have. :(
If this turns up on master we can probably get what we need then.
Updated by John Spray over 7 years ago
- Status changed from New to Can't reproduce
Haven't seen this failure in a long time.
Actions