Project

General

Profile

Feature #36352

client: explicitly show blacklisted state via asok status command

Added by Zhi Zhang 2 months ago. Updated 2 months ago.

Status:
Pending Backport
Priority:
Normal
Assignee:
Category:
Correctness/Safety
Target version:
Start date:
Due date:
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
mimic,luminous
Reviewed:
Affected Versions:
Component(FS):
ceph-fuse
Labels (FS):
task(easy)
Pull request ID:

Description

In some unstable network enviroment, we found ceph-fuse client may become blacklisted. And common users found client didn't work, but they didn't know and undertand what happened.

[ceph@xxx ~]$ ls -l /mnt/
ls: cannot access /mnt/cephfs: No such file or directory
...
d????????? ? ?    ?       ?            ? cephfs
...
[ceph@xxx ~]$ ls -l /mnt/cephfs 
ls: cannot access /mnt/cephfs: No such file or directory

So we try to explicitly show blacklisted state via asok status command to let common users to know and understand their clients state.


Related issues

Copied to fs - Backport #36456: luminous: client: explicitly show blacklisted state via asok status command In Progress
Copied to fs - Backport #36457: mimic: client: explicitly show blacklisted state via asok status command Resolved

History

#2 Updated by Patrick Donnelly 2 months ago

  • Status changed from New to Pending Backport
  • Assignee set to Zhi Zhang
  • Target version set to v14.0.0
  • Start date deleted (10/09/2018)
  • Backport set to mimic,luminous
  • Labels (FS) task(easy) added

#3 Updated by Nathan Cutler 2 months ago

  • Copied to Backport #36456: luminous: client: explicitly show blacklisted state via asok status command added

#4 Updated by Nathan Cutler 2 months ago

  • Copied to Backport #36457: mimic: client: explicitly show blacklisted state via asok status command added

Also available in: Atom PDF