Project

General

Profile

Bug #18578

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

Added by Zheng Yan 2 months ago. Updated about 2 months ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/18/2017
Due date:
% Done:

0%

Source:
Tags:
Backport:
kraken, jewel
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Release:
Component(FS):
Needs Doc:
No

Description

An user said he encountered this assertion while running vdbench


Related issues

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

History

#1 Updated by Zheng Yan 2 months ago

  • Status changed from New to Need Review

#2 Updated by John Spray about 2 months ago

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

#3 Updated by Nathan Cutler about 2 months ago

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

#4 Updated by Nathan Cutler about 2 months ago

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

Also available in: Atom PDF