Project

General

Profile

Actions
Copy link

Bug #62164

closed

qa: "cluster [ERR] MDS abort because newly corrupt dentry to be committed: [dentry #0x1/a [fffffffffffffff6,head] auth (dversion lock) v=13..."

Added by Patrick Donnelly 10 months ago. Updated 5 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Patrick Donnelly
Category:
-
Target version:
Ceph - v19.0.0
% Done:

100%

Source:
Q/A
Tags:
backport_processed
Backport:
reef,quincy,pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
qa-failure
Pull request ID:
52638
Crash signature (v1):
Crash signature (v2):

Description

/teuthology/yuriw-2023-07-20_14:36:46-fs-wip-yuri-testing-2023-07-19-1340-pacific-distro-default-smithi/7344784/1$

This is an expected cluster warning when doing these damage tests. The problem is that the MDS aborts usually before the cluster log entry can be sent off to the monitors. So we almost never see this.

A wait needs to be added and the warning ignorelisted.

Related issues 5 (1 open — 4 closed)

Has duplicate CephFS - Bug #62160: mds: MDS abort because newly corrupt dentry to be committedDuplicatePatrick Donnelly

Actions
Blocks CephFS - Bug #62208: mds: use MDSRank::abort to ceph_abort so necessary sync is doneFix Under ReviewPatrick Donnelly

Actions
Copied to CephFS - Backport #62852: reef: qa: "cluster [ERR] MDS abort because newly corrupt dentry to be committed: [dentry #0x1/a [fffffffffffffff6,head] auth (dversion lock) v=13..."ResolvedPatrick DonnellyActions
Copied to CephFS - Backport #62853: quincy: qa: "cluster [ERR] MDS abort because newly corrupt dentry to be committed: [dentry #0x1/a [fffffffffffffff6,head] auth (dversion lock) v=13..."ResolvedPatrick DonnellyActions
Copied to CephFS - Backport #62854: pacific: qa: "cluster [ERR] MDS abort because newly corrupt dentry to be committed: [dentry #0x1/a [fffffffffffffff6,head] auth (dversion lock) v=13..."ResolvedPatrick DonnellyActions
Actions
Copy link

Also available in: Atom PDF