Hey,
I'm trying to find the last two objects on an old data pool for a cephfs
cluster that seemingly aren't found via find && getfattr.
More generically though, is there a low level tool or (C++ or Python)
library for reading and analyzing cephfs metadata?
Daniel
I don't remember how connected the dashboard is to the orchestrator in
pacific, but the only thing I could think to do here is just restart it.
(ceph mgr module disable dashboard, ceph mgr module enable dashboard). You
could also totally fail over the mgr (ceph mgr fail) although that might
change
Ceph Pacific
Thanks to some misplaced thumbs-on-keyboard, I inadvertently managed to
alias a non-ceph system's ip as a ceph host and ceph adopted it
somehow.
I fixed the fat-fingered IP, and have gone through the usual motions to
delete a host, but some parts of the ceph ecosystem haven't caught
Hi Etienne,
indeed, even ```rados ls --pool test``` hangs on the same instruction
futex(0x7ffc2de0cb10, FUTEX_WAIT_BITSET_PRIVATE, 0, {tv_sec=10215,
tv_nsec=619004859},
FUTEX_BITSET_MATCH_ANY
Yes, by netcat I have checked from client side and all OSD ports are succeed
Hi Etienne,
indeed, even ```rados ls --pool test``` hangs on the same instruction
futex(0x7ffc2de0cb10, FUTEX_WAIT_BITSET_PRIVATE, 0, {tv_sec=10215,
tv_nsec=619004859}, FUTEX_BITSET_MATCH_ANY
Yes, by netcat I have checked from client side and all OSD ports are succeeded.
Hi,
By netcat I can see that OSD and MON ports are open.
You check from your client?
You can use rados cli to ensure your client can actually use your ceph cluster.
Étienne
From: service.pl...@ya.ru
Sent: Friday, 21 June 2024 11:39
To: ceph-users@ceph.io
Hi everyone! I've encountered situation I cannot even google.
In a nutshell, rbd map test/kek --id test hags forever on
```futex(0x7ffdfa73d748, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0,
NULL, FUTEX_BITSET_MATCH_ANY``` instruction in strace.
Of course, I have all the keyrings and
Hi,
This type of incident is often resolved by setting the public_network
option to the "global" scope, in the configuration:
ceph config set global public_network a:b:c:d::/64
Le ven. 21 juin 2024 à 03:36, Eugen Block a écrit :
> Hi,
>
> this only a theory, not a proven answer or something.
Hi,
maybe not a direct answer to your question.
But i would generally recommend you to verify your ceph config with our
ceph analyzer.
Simply upload your ceph report there and in a few seconds you will receive
feedback on the configuration:https://analyzer.clyso.com/
*Joachim Kraftmayer*
a:
