Bug #55779: fuse client losing connection to mds - CephFS - Ceph

Actions

Copy link

Bug #55779

open

fuse client losing connection to mds

Added by Milind Changire almost 2 years ago. Updated 7 months ago.

Status:

Need More Info

Priority:

Normal

Assignee:

Kotresh Hiremath Ravishankar

Category:

Correctness/Safety

Target version:

% Done:

Source:

Tags:

Backport:

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Component(FS):

ceph-fuse

Labels (FS):

Pull request ID:

Crash signature (v1):

Crash signature (v2):

Description

fuse client losing connection to mds after about 5 minutes of I/O

no stack trace in mds logs
no mds crashes

Actions

Copy link

Updated by Venky Shankar almost 2 years ago

Status changed from New to Need More Info

The client might be getting blocklisted. Could you share the client/mds logs?

Actions

Copy link

Updated by Milind Changire almost 2 years ago

Venky Shankar wrote:

The client might be getting blocklisted. Could you share the client/mds logs?

Here are the logs:
ceph-post-file: 35edb9f5-6e3b-4e0c-9dac-733dc0963527

Actions

Copy link

Updated by Venky Shankar almost 2 years ago

The MDS got a termination signal. E.g.: mds.a:

2022-05-29T22:18:09.220+0530 7ff3eae14640 -1 received  signal: Terminated from  (PID: 70532) UID: 25405
2022-05-29T22:18:09.220+0530 7ff3eae14640 -1 mds.a *** got signal Terminated ***
2022-05-29T22:18:09.220+0530 7ff3eae14640  1 mds.a suicide! Wanted state up:active
2022-05-29T22:18:09.220+0530 7ff3eae14640  5 mds.beacon.a set_want_state: up:active -> down:dne
2022-05-29T22:18:09.220+0530 7ff3eae14640  5 mds.beacon.a Sending beacon down:dne seq 88

Who is PID 70532?

Actions

Copy link