Ah right, in 18.2.0 the event wasn't present, that explains it. I
won't fail the customer cluster, of course. Everything is fine, I was
just curious what the many many events were. Althouh there's barely
any IO to the CephFS, it still logs between 16k and 60k events in
daemonperf output.
Anyway, thanks again for your quick response!
Zitat von Venky Shankar <[email protected]>:
On Fri, Jun 19, 2026 at 3:02 PM Eugen Block <[email protected]> wrote:
Thanks for your quick response!
The ceph-common version is 18.2.0 (Ubuntu Jammy). I tried the same
within cephadm shell (19.2.3) and there I get a "operation not
permitted":
root@ceph-osd-1:/# ceph -v
ceph version 19.2.3 (c92aebb279828e9c3c1f5d24613efca272649e62)
squid (stable)
root@ceph-osd-1:/# cephfs-journal-tool --rank=cephfs:0 event get list
Error ((1) Operation not permitted2026-06-19T09:26:02.373+0000
7f25d078b380 -1 main: Cannot run cephfs-journal-tool on an active file
system!
)
Why can I list events from outside the shell? I'm a bit surprised.
Because of "Cannot run cephfs-journal-tool on an active file system!".
This check was added because some users ran the tool (with other
arguments) on an active file system, which caused various issues. Do a
`ceph fs fail ...` and the tool should work.
Zitat von Venky Shankar <[email protected]>:
> Hi Eugen,
>
> On Fri, Jun 19, 2026 at 2:27 PM Eugen Block via ceph-users
> <[email protected]> wrote:
>>
>> Hi,
>>
>> I am currently looking into MDS warnings (behind on trimming) on a
>> customer cluster. They recently upgraded to Squid 19.2.3 which seems
>> to have fixed a bug with trimming, so the warning doesn't come that
>> often anymore (if at all currently). But when digging a bit deeper, I
>> noticed these messages in the event get list output:
>>
>> cephfs-journal-tool --rank=cephfs:0 event get list | head
>> 2026-06-18T13:12:22.821+0000 7fec1b5ff280 0 uh oh, unknown log event
>> type 100 length 14
>> 2026-06-18T13:12:22.833+0000 7fec1b5ff280 0 uh oh, unknown log event
>> type 100 length 14
>
> What version is cephfs-journal-tool (--version) and is it the same
> version as (or close to) the ceph cluster?
>
>>
>> That message is repeated 118 times or so before dumping the actual
>> event list. I looked at the code for 19.2.0 [0] and 19.2.3 [1], in
>> both cases event type 100 seems to be defined:
>>
>> #define EVENT_SEGMENT 100
>>
>> So why is it unknown? It doesn't appear to have any negative impact,
>> at least noone has complained yet, but I still wanted to ask what this
>> is about. Can I ignore this? Will that go away on its own at some point?
>>
>> Any pointers are appreciated!
>>
>> Thanks!
>> Eugen
>>
>> [0] https://github.com/ceph/ceph/blob/v19.2.0/src/mds/LogEvent.h#L45
>> [1] https://github.com/ceph/ceph/blob/v19.2.3/src/mds/LogEvent.h#L45
>> _______________________________________________
>> ceph-users mailing list -- [email protected]
>> To unsubscribe send an email to [email protected]
_______________________________________________
ceph-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
