mirror of
https://github.com/ceph/ceph
synced 2024-12-26 05:25:09 +00:00
f1b6bd7988
Maximum object size is 100GB configurable with osd_max_object_size Error EFBIG if attempt to WRITE/WRITEFULL/TRUNCATE beyond osd_max_object_size Error EINVAL if length < 1 for WRITE/WRITEFULL/ZERO Make ZERO beyond existing size a no-op Fixes: #5252 Fixes: #5340 Signed-off-by: David Zafman <david.zafman@inktank.com> Reviewed-by: Sage Weil <sage@inktank.com>
32 lines
1.0 KiB
Plaintext
32 lines
1.0 KiB
Plaintext
|
|
v0.65
|
|
-----
|
|
|
|
* Huge revamp of the 'ceph' command-line interface implementation.
|
|
|
|
* The 'ceph osd tell ...' and 'ceph mon tell ...' commands are no
|
|
longer supported. Any callers should use::
|
|
|
|
ceph tell osd.<id or *> ...
|
|
ceph tell mon.<id or name or *> ...
|
|
|
|
The 'ceph mds tell ...' command is still there, but will soon also
|
|
transition to 'ceph tell mds.<id or name or *> ...'
|
|
|
|
* The 'ceph osd crush add ...' command used to take one of two forms::
|
|
|
|
ceph osd crush add 123 osd.123 <weight> <location ...>
|
|
ceph osd crush add osd.123 <weight> <location ...>
|
|
|
|
This is because the id and crush name are redundant. Now only the
|
|
simple form is supported, where the osd name/id can either be a bare
|
|
id (integer) or name (osd.<id>)::
|
|
|
|
ceph osd crush add osd.123 <weight> <location ...>
|
|
ceph osd crush add 123 <weight> <location ...>
|
|
|
|
* There is now a maximum RADOS object size, configurable via 'osd max
|
|
object size', defaulting to 100 GB. Note that this has no effect on
|
|
RBD, CephFS, or radosgw, which all stripe over objects.
|
|
|
|
|