Project

General

Profile

Actions
Copy link

Bug #42559

closed

kernel rbd unmap command for force option will show Invalid argument

Added by Duncan Chiang over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Ilya Dryomov
Category:
rbd
Target version:
-
% Done:

0%

Source:
Community (dev)
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
Ceph - v14.2.4
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):

Description

In Ceph version 14.2.4 (75f4de193b3ea58512f204623e6c5a16e6c1e1ba) nautilus (stable)

When I use rbd unmap command with force option, will show below error message

# rbd unmap /dev/rbd0 -o force
rbd: sysfs write failed
rbd: unmap failed: (22) Invalid argument
Actions
Copy link
 #1

Updated by Brad Hubbard over 4 years ago

  • Project changed from Ceph to Linux kernel client
  • Category set to rbd
Actions
Copy link
 #2

Updated by Ilya Dryomov over 4 years ago

  • Assignee set to Ilya Dryomov

Which kernel is this on? Is there anything in dmesg?

Actions
Copy link
 #3

Updated by Duncan Chiang over 4 years ago

My env os is ubuntu 16.04
I tested in 4.4.0-142-generic is failed

But I tested in 4.15.0-66-generic is Ok now.

Maybe my env should be update kernel version...

Very thanks

Actions
Copy link
 #4

Updated by Duncan Chiang over 4 years ago

And I checked the dmesg log is show nothing...

Actions
Copy link
 #5

Updated by Ilya Dryomov over 4 years ago

  • Status changed from New to Closed

Yes, -o force was introduced in 4.9. Be aware that it isn't a generic "unmap no matter what" option, the only thing it does is it bypasses the "is this device still open" check.

Actions
Copy link
 #6

Updated by Duncan Chiang over 4 years ago

Ilya Dryomov wrote:

Yes, -o force was introduced in 4.9. Be aware that it isn't a generic "unmap no matter what" option, the only thing it does is it bypasses the "is this device still open" check.

Thanks your help, Ilya.

Actions
Copy link

Also available in: Atom PDF