Project

General

Profile

Actions
Copy link

Bug #25187

closed

Mimic rbd failed to create image in format 1

Added by Yecheng Fu over 5 years ago. Updated over 5 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

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

Description

client:

```
  1. rbd --version
    ceph version 13.2.1 (5533ecdc0fda920179d7ad84e0aa65a127b20d77) mimic (stable)
  2. uname -a
    Linux xq42 4.4.0-72-generic #93-Ubuntu SMP Fri Mar 31 14:07:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
    ```

server:

```
root@xq45:~# ceph --version
ceph version 10.2.9 (2ee413f77150c0f375ff6f10edd6c8f9c7d060d0)
```

Error log:

```
  1. rbd -m 192.168.162.30:6789,192.168.162.35:6789,192.168.162.36:6789 -p kube --id admin --key <key> create testimg --size 1024
    rbd: image format 1 is deprecated
    2018-07-31 04:07:44.784 7fcae8a44900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
    2018-07-31 04:07:44.788 7fcae8a44900 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin,: (2) No such file or directory
    rbd: create error: 2018-07-31 04:07:44.792 7fcae8a44900 -1 librbd: Format 1 image creation unsupported.
    (22) Invalid argument
    ```

Although image format 1 is deprecated, but I think it should be supported anyway.

I can create image in image format 1 with luminous rbd.

Actions
Copy link
 #1

Updated by Yecheng Fu over 5 years ago

typo: minic -> mimic

Actions
Copy link
 #2

Updated by John Spray over 5 years ago

  • Project changed from Ceph to rbd
  • Subject changed from Minic rbd failed to create image in format 1 to Mimic rbd failed to create image in format 1
  • Status changed from New to Rejected

This doesn't appear to be a bug. If there's a strong reason to re-think disabling v1 image creation I'd suggest bringing it up on the mailing list.

Actions
Copy link
 #3

Updated by Jason Dillaman over 5 years ago

This was a conscience decision since we want to remove all support for v1 images (there is wasted effort in maintaining and testing v1 image support) -- there should be zero need to ever use them.

Actions
Copy link
 #4

Updated by Yecheng Fu over 5 years ago

Thanks for clarification!

I decided to migrate to image format 1.

This issue can be closed. Thanks again!

Actions
Copy link

Also available in: Atom PDF