Project

General

Profile

Actions

Bug #50353

open

rbd: listing images failed: (2) No such file or directory

Added by Adrian Dabuleanu about 3 years ago. Updated about 3 years ago.

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

0%

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

Description

While looking at the rbd images, I found a lot of errors with "No such file or directory" while running the command: rbd list -h <pool-name>

Some intermediary errors include

2021-04-14T12:12:33.313+0000 7f8e0effd700 -1 librbd::io::AioCompletion: 0x55de121839a0 fail: (2) No such file or directory
rbd: error opening volume-44c2f74c-0c2c-4237-9582-96da9c3cbc64: (2) No such file or directory

Please see attached log file (crash1.log) for more details.

As a side note, we are using Openstack with a ceph storage backend, and noticed that the ceph storage increased over time although this did not reflect the Openstack usage. This was the trigger which lead to this finding on ceph rbd.

Sorry in advance, if I did not create the ticket correctly. It is my first time opening a bug on this project.


Files

crash1.log (88.8 KB) crash1.log ceph rbs ls -f Adrian Dabuleanu, 04/14/2021 12:23 PM
Actions #1

Updated by Adrian Dabuleanu about 3 years ago

Adrian Dabuleanu wrote:

While looking at the rbd images, I found a lot of errors with "No such file or directory" while running the command: rbd list -f <pool-name>

Some intermediary errors include

2021-04-14T12:12:33.313+0000 7f8e0effd700 -1 librbd::io::AioCompletion: 0x55de121839a0 fail: (2) No such file or directory
rbd: error opening volume-44c2f74c-0c2c-4237-9582-96da9c3cbc64: (2) No such file or directory

Please see attached log file (crash1.log) for more details.

As a side note, we are using Openstack with a ceph storage backend, and noticed that the ceph storage increased over time although this did not reflect the Openstack usage. This was the trigger which lead to this finding on ceph rbd.

Sorry in advance, if I did not create the ticket correctly. It is my first time opening a bug on this project.

Actions

Also available in: Atom PDF