System attributes shown as "object_info", "snapset" and "hashinfo"
Only output user attributes as "attrs"
Drop leading undescore "_" for user attribute keys
Improve logic as to when to show user attributes or specific system attributes
Signed-off-by: David Zafman <dzafman@redhat.com>
* refs/pull/21315/head:
qa/tasks/mgr/test_failover: fix for id -> name rename in mgr metadata
Reviewed-by: John Spray <john.spray@redhat.com>
Reviewed-by: Jan Fajerski <jfajerski@suse.com>
* refs/pull/21080/head:
src: Added const references to various function parameters
Reviewed-by: Kefu Chai <kchai@redhat.com>
Reviewed-by: Patrick Donnelly <pdonnell@redhat.com>
This gets called during chdir and is currently a no-op. Make sure we
check permissions appropriately.
Tracker: http://tracker.ceph.com/issues/23509
Signed-off-by: Jeff Layton <jlayton@redhat.com>
Add a validity check for 'auth add' and 'fs authorize'. 'auth caps' and
'auth get-or-create[-key]' already had the check.
Fixes: http://tracker.ceph.com/issues/22525
Signed-off-by: Sage Weil <sage@redhat.com>
Also strenghen the check to declare an unknown cap type as invalid.
Note that this means that in a mixed-version cluster, an older mon
would apply the syntax check for the older caps, even if the (say) OSDs
are newer and could parse something different. This is judged to be fine:
it is not unreasonable to ask for the mons *and* daemons to be upgraded
before using the new cap syntax or feature.
Signed-off-by: Jing Li <lijing@gohighsec.com>
Signed-off-by: Sage Weil <sage@redhat.com>
if the osd_pgtemp message is dropped before monitor receives it, we need
to resend it. otherwise a pg could be stuck in activating state if the
pg creation was withheld by the max-pg-per-osd on the replica, and then
the replica osd removes some existing pg.
Fixes: http://tracker.ceph.com/issues/23610
Signed-off-by: Kefu Chai <kchai@redhat.com>
Assume we have a pool of crush-failure-domain OSD, then the stack will look like:
[
"0":"8" // stack[0]
"0":"1" // stack[1]
]
The above stack is error-prone because when passed to _choose_type_stack(),
iterator **i** shall already point to orig.end() when stack[0] is done
and might still get incremented while we continues to handle stack[1], and
hence produce the following abnormal (**overflowed**) mapping results:
```
-36> 2018-04-06 23:06:35.041274 7f84692bd700 10 total_deviation 24.6667 overfull 4,5,6,7,8 underfull [2,0,3,9]
-35> 2018-04-06 23:06:35.041278 7f84692bd700 10 osd.7 move 3
-34> 2018-04-06 23:06:35.041280 7f84692bd700 10 trying 2.0
-33> 2018-04-06 23:06:35.041310 7f84692bd700 10 2.0 [3,5,6,4,9,0,7,10] -> [1953720676,1683976050,1919120229,1769238633,838889071,3224629,101,2]
-32> 2018-04-06 23:06:35.041317 7f84692bd700 10 2.0 pg_upmap_items [3,1953720676,5,1683976050,6,1919120229,4,1769238633,9,838889071,0,3224629,7,101,10,2]
```
See also:
http://pulpito.ceph.com/yuriw-2018-04-06_21:35:03-rados-wip-yuri2-testing-2018-04-06-1946-luminous-distro-basic-smithi/2365151/
Signed-off-by: xie xingguo <xie.xingguo@zte.com.cn>
In choose_leaf mode we normally should have a stack of 2 and
hence below here we still need to re-check the iterator against
the stack loop.
Signed-off-by: xie xingguo <xie.xingguo@zte.com.cn>
cephfs-foo-tool from current master crashes immediately it starts.
Introduced by commit 6972273d53 "global: output usage on -h, --help,
or no args before contacting mons"
Signed-off-by: "Yan, Zheng" <zyan@redhat.com>
Fixes: http://tracker.ceph.com/issues/23624
to pick up
- bug fixes since 5.8.0
- crc32c_3way introduced in 5.9.0 for better performance on platforms
with PCLMULQDQ support.
- the fixes for silencing the fallthrough warnings when compiling with
GCC-7
for detailed changelog since 5.8.0, see
https://github.com/facebook/rocksdb/blob/master/HISTORY.md
Signed-off-by: Kefu Chai <kchai@redhat.com>
in python3, the stuff read from wire is represented as "bytes", but
the output of "ceph -w" is supposed to be consumed by human. so decode
it as utf-8.
Signed-off-by: Kefu Chai <kchai@redhat.com>
