Keep the result size check for a while since older OSDs won't populate
the pmore field for us. Eventually we can remove it.
Signed-off-by: Sage Weil <sage@redhat.com>
msg/simple/Pipe:the returned value for do_recv unequal to zero
Reviewed-by: Loic Dachary <loic@dachary.org>
Reviewed-by: Gregory Farnum <gfarnum@redhat.com>
Reviewed-by: Kefu Chai <kchai@redhat.com>
the short ids of old, removed zones were being kept in the period to
guard against hash collisions with new zones
but for a hash collision to cause a wrong object to sync, that object
would have to be uploaded simultaneously to two different zones that had
the same short id
to avoid this, we just have to prevent the period from containing two
colliding zones at the same time - we don't have to remember old zone
short ids forever
Fixes: http://tracker.ceph.com/issues/15618
Signed-off-by: Casey Bodley <cbodley@redhat.com>
this was breaking the versioned object test in test_multi.py, because we
were trying to create delete markers instead of unlinking a specific
object instance
Signed-off-by: Casey Bodley <cbodley@redhat.com>
rbd: prevent adding multiple mirror peers to a single pool
Reviewed-by: Dongsheng Yang <dongsheng.yang@easystack.cn>
Reviewed-by: Mykola Golub <mgolub@mirantis.com>
build/ops: make package groups comply with openSUSE guidelines
Reviewed-by: Ken Dreyer <kdreyer@redhat.com>
Reviewed-by: Boris Ranto <branto@redhat.com>
The rbd-mirror daemon does not currently support replication
from multiple peers. Until that is supported, add a temporary
restriction to prevent confusion.
Fixes: http://tracker.ceph.com/issues/19256
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
silence following warning:
store_test.cc: In member function ‘virtual void
StoreTest_ManyObjectTest_Test::TestBody()’:
/var/ceph/ceph/src/test/objectstore/store_test.cc:3153:6: warning:
suggest explicit braces to avoid ambiguous ‘else’ [-Wdangling-else]
if (listed2.size())
^
Signed-off-by: Kefu Chai <kchai@redhat.com>
/sys/bus/rbd/supported_features is available on kernels starting with
4.11. Example output:
$ sudo rbd map x
rbd: sysfs write failed
RBD image feature set mismatch. This image cannot be mapped because the following immutable features are unsupported by the kernel: data-pool.
In some cases useful info is found in syslog - try "dmesg | tail".
rbd: map failed: (6) No such device or address
$ sudo rbd map -p foo y
rbd: sysfs write failed
RBD image feature set mismatch. You can disable features unsupported by the kernel with "rbd feature disable foo/y object-map fast-diff deep-flatten".
In some cases useful info is found in syslog - try "dmesg | tail".
rbd: map failed: (6) No such device or address
or, if /sys/bus/rbd/supported_features isn't there:
$ sudo rbd map z
rbd: sysfs write failed
RBD image feature set mismatch. Try disabling features unsupported by the kernel with "rbd feature disable".
In some cases useful info is found in syslog - try "dmesg | tail".
rbd: map failed: (6) No such device or address
Fixes: http://tracker.ceph.com/issues/19095
Signed-off-by: Ilya Dryomov <idryomov@gmail.com>
when transitioning to incremental sync, we need to write temp_marker
instead of sync_marker, because temp_marker has replaced the full sync
marker (which is a metadata key, rather than an log marker) with
next_step_marker
this was breaking the metadata checkpoint in test_multi.py, because it
was comparing metadata keys (i.e. 'user:zone.user') against mdlog
markers
Signed-off-by: Casey Bodley <cbodley@redhat.com>
It was possible for multiple, concurrent acquire attempts to be
running for a single instance due to notification messages. Now
only a single acquire state machine can be running.
Signed-off-by: Jason Dillaman <dillaman@redhat.com>
