Project

General

Profile

Actions

Bug #10387

closed

ceph-fuse doesn't release capability on deleted directory

Added by John Spray over 9 years ago. Updated over 9 years ago.

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

0%

Source:
Development
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Component(FS):
Labels (FS):
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

I thought this was a repeat of #10164, but then noticed that the dirfrag objects were deleted once the client unmounted.

I've added a workaround for this in the new mds_flush test task, which checks that deletion results in objects going away after a flush.

From looking at client logs, it appears that the client simply does not release the capability on a directory when it deletes it, so the MDS can't purge the stray directory.

Actions #1

Updated by John Spray over 9 years ago

  • Project changed from Ceph to CephFS
Actions #2

Updated by Zheng Yan over 9 years ago

  • Status changed from New to In Progress
Actions #3

Updated by Zheng Yan over 9 years ago

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

Updated by Greg Farnum over 9 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Assignee set to Zheng Yan
  • Source changed from other to Development

This was merged to master in commit:e9a29c58b6d40933afbf711afcf7b872b4005585; does it need a backport?

Actions #5

Updated by Zheng Yan over 9 years ago

do we need to backport this. the directory will be deleted when all of its child dentries get trimmed from the cache

Actions #6

Updated by John Spray over 9 years ago

I wouldn't bother backporting: the symptom is just some dir objects that don't get cleaned up until next client unmount, so it doesn't break the world for users.

Actions #7

Updated by Zheng Yan over 9 years ago

  • Status changed from Pending Backport to Resolved
Actions

Also available in: Atom PDF