Project

General

Profile

Actions
Copy link

Bug #52303

closed

Client should fail mounts on misunderstood mdsmap updates

Added by Greg Farnum over 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Jeff Layton
Category:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

Right now, if the kernel client doesn't understand an mdsmap, it just prints out an error message, drops the map, and continues.

Obviously, if this happens, something has gone very wrong. Continuing to do IO is likely to cause issues; we should treat the mount as failed instead.

Actions
Copy link
 #1

Updated by Jeff Layton over 2 years ago

  • Priority changed from Urgent to Normal

Downgrading priority. We definitely have bigger fish to fry than this one.

Actions
Copy link
 #2

Updated by Jeff Layton over 2 years ago

  • Status changed from New to In Progress

I think we can just hijack the machinery that handles "umount -f" to do this. I'll take a stab at a patch for it soon.

Actions
Copy link
 #3

Updated by Jeff Layton over 2 years ago

  • Status changed from In Progress to Fix Under Review
Actions
Copy link
 #4

Updated by Xiubo Li almost 2 years ago

  • Status changed from Fix Under Review to Resolved
  • Assignee set to Jeff Layton

Patch has been merged and mark it as resolved.

Actions
Copy link

Also available in: Atom PDF