Bug #1701
open
krbd: limits and constants are not consistent in kernel and userspace
Added by Josh Durgin over 12 years ago.
Updated over 9 years ago.
Description
There are a few things that exist in the kernel but not userspace:
- SNAP_NAME_LEN
- (MIN|MAX)_OBJECT_ORDER
Also, image name length is 96 in the kernel, but not enforced on the userspace side.
There are probably more issues like this that need fixing, and the limits should be documented.
Instead of opening a new issue, I think I can add it here.
Besides those limits on the RBD images, there's also a hardcoded limit in libceph (messenger.c).
Object name (oid) is limited to 40 chars, so even though an RBD image can be up to 96 chars (100 with the suffix), the name is truncated, and the mapping will fail with ENOENT.
Stratos Psomadakis wrote:
Instead of opening a new issue, I think I can add it here.
Besides those limits on the RBD images, there's also a hardcoded limit in libceph (messenger.c).
Object name (oid) is limited to 40 chars, so even though an RBD image can be up to 96 chars (100 with the suffix), the name is truncated, and the mapping will fail with ENOENT.
That's actually in teh kernel code, so i'll make a separate issue for it. Thanks!
Also related: we have MAX_POOL_NAME_SIZE and MAX_SNAP_NAME_SIZE as 128 in qemu right now.
- Translation missing: en.field_position set to 33
- Translation missing: en.field_position deleted (
74)
- Translation missing: en.field_position set to 54
- Project changed from Ceph to rbd
- Category deleted (
librbd)
- Assignee set to Alex Elder
- Assignee deleted (
Alex Elder)
- Project changed from rbd to Linux kernel client
- Subject changed from rbd: limits and constants are not consistent in kernel and userspace to krbd: limits and constants are not consistent in kernel and userspace
Also available in: Atom
PDF