Project

General

Profile

Bug #18578

failed filelock.can_read(-1) assertion in Server::_dir_is_nonempty

Added by Zheng Yan almost 6 years ago. Updated over 5 years ago.

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

0%

Source:
Tags:
Backport:
kraken, jewel
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

An user said he encountered this assertion while running vdbench


Related issues

Copied to CephFS - Backport #18707: kraken: failed filelock.can_read(-1) assertion in Server::_dir_is_nonempty Resolved
Copied to CephFS - Backport #18708: jewel: failed filelock.can_read(-1) assertion in Server::_dir_is_nonempty Resolved

History

#1 Updated by Zheng Yan almost 6 years ago

  • Status changed from New to Fix Under Review

#2 Updated by John Spray almost 6 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to kraken, jewel

#3 Updated by Nathan Cutler almost 6 years ago

  • Copied to Backport #18707: kraken: failed filelock.can_read(-1) assertion in Server::_dir_is_nonempty added

#4 Updated by Nathan Cutler almost 6 years ago

  • Copied to Backport #18708: jewel: failed filelock.can_read(-1) assertion in Server::_dir_is_nonempty added

#5 Updated by Nathan Cutler over 5 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF