- ceph-users - lists.ceph.io

Ceph Roundup: Umbrella Summit, Windows Survey, Cephalocon & More!
by Anthony Middleton 22 Aug '25

22 Aug '25

Hey Cephers, Welcome to my first *Ceph Roundup! *This is your one-stop update for everything happening in our community. I plan to send this type of email weekly, or as often as needed. Here's what's making waves this week: *Ceph Developer Summit: Umbrella* The Summit runs from *Sept 3–12 (virtual)*. Join the conversation, shape the next release, and collaborate with fellow Cephers! Schedule coming soon! Read more here: https://ceph.io/en/community/events/2025/ceph-developer-summit-umbrella/ *Windows Support for Ceph – Community Survey* We're exploring Windows support! Your input helps guide this effort. Survey -https://forms.gle/ME2tqW12zavCorDd8 *Cephalocon 2025 Registration is OPEN!* Get ready for our flagship event. Secure your spot and meet Cephers from around the world. Register now - https://events.linuxfoundation.org/cephalocon/register/ *Cephalocon Sponsorship Opportunities* Want to showcase your brand at the biggest Ceph event of the year? Sponsorships are still available until September 31st! Learn more - https://events.linuxfoundation.org/cephalocon/sponsor/ That's it for this week! Share your experience with Ceph in a message below. Did you learn anything new? What Ceph project are you starting next week? Your insights help us keep Ceph thriving. Stay squiddy, --- Anthony Middleton Ceph Community Manager 🐙 LinkedIn <https://www.linkedin.com/in/middleton-anthony/>| BlueSky <https://bsky.app/profile/anthonymicmidd.bsky.social> community-manager(a)ceph.io

1 0

Problems afte update Debian bullseye to trixie and quinct to reef
by Christian Peters 22 Aug '25

22 Aug '25

Hi all, not sure it's ok to ask questions here as we are only a little Theater where I manage the data of our sound and video files. I set up a ceph cluster as second backup location on bullseye with quincy which worked flawless. All runs smooth but I thought I would have to do a step forward to get on track. Yes I know: never change a running system. :-D After updating all three nodes I forget to set the ceph packages on hold so they were updated to reef with trixie. No way to downgrade ...I tried a lot....! So I went forward. After all all 3 nodes are back online running reef my cluster seems to work, my cephfs share is reachable by my client machine, backups are working. This is my ceph status output: cluster: id: c5986871-ab9f-4365-8113-a1854fa07786 health: HEALTH_WARN 15 mgr modules have failed dependencies services: mon: 3 daemons, quorum ceph1,ceph2,ceph3 (age 19h) mgr: ceph1(active, since 18h), standbys: ceph2, ceph3 mds: 1/1 daemons up, 2 standby osd: 24 osds: 24 up (since 19h), 24 in (since 22M) data: volumes: 1/1 healthy pools: 3 pools, 1041 pgs objects: 3.34M objects, 11 TiB usage: 32 TiB used, 56 TiB / 87 TiB avail pgs: 1041 active+clean Problem: dashboard is not working any more and I have this erre/warn: 15 mgr modules have failed dependencies The cluster was made without podman/containers. ceph-crash gives me a flood of this errors: ... WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T11:51:45.411885Z_738ee242-f7bd-4f6c-bd90-d96a08e06bf6 as client.admin failed: 2025-08-22T06:55:50.234+0000 7ff72cea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.234+0000 7ff72cea96c0 -1 AuthRegistry(0x7ff728064068) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.238+0000 7ff72cea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.238+0000 7ff72cea96c0 -1 AuthRegistry(0x7ff728068540) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.238+0000 7ff72cea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.238+0000 7ff72cea96c0 -1 AuthRegistry(0x7ff72cea8410) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:54:08.817091Z_34eaeca9-7883-4b93-b75d-83102c113baa as client.crash.ceph1 failed: 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 AuthRegistry(0x7f81ac0640c8) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 AuthRegistry(0x7f81ac0686c0) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 AuthRegistry(0x7f81b3ea8410) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:54:08.817091Z_34eaeca9-7883-4b93-b75d-83102c113baa as client.crash failed: 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 AuthRegistry(0x7f5b9c064068) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 AuthRegistry(0x7f5b9c068540) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 AuthRegistry(0x7f5ba2ea8410) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:54:08.817091Z_34eaeca9-7883-4b93-b75d-83102c113baa as client.admin failed: 2025-08-22T06:55:50.478+0000 7fc8494fe6c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.478+0000 7fc8494fe6c0 -1 AuthRegistry(0x7fc844064068) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.482+0000 7fc8494fe6c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.482+0000 7fc8494fe6c0 -1 AuthRegistry(0x7fc844068540) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.482+0000 7fc8494fe6c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.482+0000 7fc8494fe6c0 -1 AuthRegistry(0x7fc8494fd410) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:28:14.730789Z_ad2ef583-85b7-4cf0-a2fd-2fa3b775a7a2 as client.crash.ceph1 failed: 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 AuthRegistry(0x7f83d40640c8) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 AuthRegistry(0x7f83d40686c0) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 AuthRegistry(0x7f83d9aa8410) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:28:14.730789Z_ad2ef583-85b7-4cf0-a2fd-2fa3b775a7a2 as client.crash failed: 2025-08-22T06:55:50.642+0000 7f2a37aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.642+0000 7f2a37aa96c0 -1 AuthRegistry(0x7f2a30064068) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.646+0000 7f2a37aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.646+0000 7f2a37aa96c0 -1 AuthRegistry(0x7f2a30068540) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.646+0000 7f2a37aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.646+0000 7f2a37aa96c0 -1 AuthRegistry(0x7f2a37aa8410) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:28:14.730789Z_ad2ef583-85b7-4cf0-a2fd-2fa3b775a7a2 as client.admin failed: 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 AuthRegistry(0x7fa800064068) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 AuthRegistry(0x7fa800068540) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 AuthRegistry(0x7fa805ea8410) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) ...... In /etc/ceph I have ceph.client.admin.keyring ceph.conf rbdmap Maye there is a way to fix this but if it's to complicated I will think about a complete re-install. I'm not an admin but an amateur with some linux knowledge. If there is hope and someone could support to solev this I would be very happy! Regards, Christian Peters

2 1

new osd's with custom device-class sata not being used by pool?
by jbuburuzlist 22 Aug '25

22 Aug '25

Hello I just added more nodes to quincy cluster(existing drives are SAS). The new nodes are sata drives. The problem is after creating a new replicated crush rule and applying to a new pool. The ceph cluster is still using osd with "hdd" class and not using sata drives. I tried a number of crush rules using replicated and EC and I cannot get the pools to use sata osds. Here is crush rule for sata: { "rule_id": 9, "rule_name": "rbdsatareplicated", "type": 1, "steps": [ { "op": "take", "item": -33, "item_name": "default~sata" }, { "op": "chooseleaf_firstn", "num": 0, "type": "host" }, { "op": "emit" } ] } I see in the crush rule "default~sata". I am wondering if this "default~" is causing me problems? Just another note. After I added the new sata nodes, my first crush rule used ec instead of replicated. I was getting errors when I tried to create a image on the ec pool "qemu-img error rbd create: Operation not supported on new pool". So I tried a test pool using replicated instead. Currently on the cluster I can create any number of pools and images if I use replicated/ec and the SAS drives which have a class of "hdd". Hope this makes sense? Here is some additional details: My existing nodes used SAS and are labelled: ceph osd tree ID CLASS WEIGHT TYPE NAME STATUS REWEIGHT PRI-AFF -1 1122.64075 root default -3 34.03793 host node-01 0 hdd 2.26920 osd.0 up 1.00000 1.00000 1 hdd 2.26920 osd.1 up 1.00000 1.00000 2 hdd 2.26920 osd.2 up 1.00000 1.00000 ..etc After adding SATA nodes I have: ID CLASS WEIGHT TYPE NAME STATUS REWEIGHT PRI-AFF -1 1122.64075 root default -3 34.03793 host node-01 0 hdd 2.26920 osd.0 up 1.00000 1.00000 1 hdd 2.26920 osd.1 up 1.00000 1.00000 2 hdd 2.26920 osd.2 up 1.00000 1.00000 .... ... -34 133.78070 host node-20 141 sata 11.14839 osd.141 up 1.00000 1.00000 142 sata 11.14839 osd.142 up 1.00000 1.00000 143 sata 11.14839 osd.143 up 1.00000 1.00000 144 sata 11.14839 osd.144 up 1.00000 1.00000 145 sata 11.14839 osd.145 up 1.00000 1.00000 146 sata 11.14839 osd.146 up 1.00000 1.00000 ... Thanks jerry

2 1

mclock scheduler on 19.2.1
by Curt 22 Aug '25

22 Aug '25

Hello all, I'm sure this has been discussed before, but I can't seem to find it. I know on older versions of Ceph there was an issue with mclock having no recovery and switching to wpq fixed it. Is this still an issue with 19.2.1? I recently ran into this bug <https://tracker.ceph.com/issues/70390>and various issues with it. In order to help recovery I set norebalance flag, so it would focus solely on undersized PGs. The issue I'm seeing though is sometimes recovering will show nothing despite having X active+undersized+remapped+backfilling. Sometimes restarting a few OSD's will fix the issue and it will start again. I'm tempted to switch to wpq, but that would mean having to slowly restart each OSD, which with undersized would cause IO to stop while some OSD's are restarted. Wanted to get others' thoughts before making the change. Thanks, Curt

2 3

Problems after update Debian bullseye to trixie and quincy to reef
by info＠hcpeters.de 22 Aug '25

22 Aug '25

Hi all, not sure it's ok to ask questions here as we are only a little Theater where I manage the data of our sound and video files. I set up a ceph cluster as second backup location on bullseye with quincy which worked flawless. All runs smooth but I thought I would have to do a step forward to get on track. Yes I know: never change a running system. :-D After updating all three nodes I forget to set the ceph packages on hold so they were updated to reef with trixie. No way to downgrade ...I tried a lot....! So I went forward. After all all 3 nodes are back online running reef my cluster seems to work, my cephfs share is reachable by my client machine, backups are working. This is my ceph status output: cluster: id: c5986871-ab9f-4365-8113-a1854fa07786 health: HEALTH_WARN 15 mgr modules have failed dependencies services: mon: 3 daemons, quorum ceph1,ceph2,ceph3 (age 19h) mgr: ceph1(active, since 18h), standbys: ceph2, ceph3 mds: 1/1 daemons up, 2 standby osd: 24 osds: 24 up (since 19h), 24 in (since 22M) data: volumes: 1/1 healthy pools: 3 pools, 1041 pgs objects: 3.34M objects, 11 TiB usage: 32 TiB used, 56 TiB / 87 TiB avail pgs: 1041 active+clean Problem: dashboard is not working any more and I have this erre/warn: 15 mgr modules have failed dependencies The cluster was made without podman/containers. ceph-crash gives me a flood of this errors: ... WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T11:51:45.411885Z_738ee242-f7bd-4f6c-bd90-d96a08e06bf6 as client.admin failed: 2025-08-22T06:55:50.234+0000 7ff72cea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.234+0000 7ff72cea96c0 -1 AuthRegistry(0x7ff728064068) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.238+0000 7ff72cea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.238+0000 7ff72cea96c0 -1 AuthRegistry(0x7ff728068540) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.238+0000 7ff72cea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.238+0000 7ff72cea96c0 -1 AuthRegistry(0x7ff72cea8410) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:54:08.817091Z_34eaeca9-7883-4b93-b75d-83102c113baa as client.crash.ceph1 failed: 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 AuthRegistry(0x7f81ac0640c8) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 AuthRegistry(0x7f81ac0686c0) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.318+0000 7f81b3ea96c0 -1 AuthRegistry(0x7f81b3ea8410) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:54:08.817091Z_34eaeca9-7883-4b93-b75d-83102c113baa as client.crash failed: 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 AuthRegistry(0x7f5b9c064068) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 AuthRegistry(0x7f5b9c068540) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.398+0000 7f5ba2ea96c0 -1 AuthRegistry(0x7f5ba2ea8410) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:54:08.817091Z_34eaeca9-7883-4b93-b75d-83102c113baa as client.admin failed: 2025-08-22T06:55:50.478+0000 7fc8494fe6c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.478+0000 7fc8494fe6c0 -1 AuthRegistry(0x7fc844064068) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.482+0000 7fc8494fe6c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.482+0000 7fc8494fe6c0 -1 AuthRegistry(0x7fc844068540) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.482+0000 7fc8494fe6c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.482+0000 7fc8494fe6c0 -1 AuthRegistry(0x7fc8494fd410) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:28:14.730789Z_ad2ef583-85b7-4cf0-a2fd-2fa3b775a7a2 as client.crash.ceph1 failed: 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 AuthRegistry(0x7f83d40640c8) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 AuthRegistry(0x7f83d40686c0) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.562+0000 7f83d9aa96c0 -1 AuthRegistry(0x7f83d9aa8410) no keyring found at /etc/ceph/ceph.client.crash.ceph1.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:28:14.730789Z_ad2ef583-85b7-4cf0-a2fd-2fa3b775a7a2 as client.crash failed: 2025-08-22T06:55:50.642+0000 7f2a37aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.642+0000 7f2a37aa96c0 -1 AuthRegistry(0x7f2a30064068) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.646+0000 7f2a37aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.646+0000 7f2a37aa96c0 -1 AuthRegistry(0x7f2a30068540) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.646+0000 7f2a37aa96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.646+0000 7f2a37aa96c0 -1 AuthRegistry(0x7f2a37aa8410) no keyring found at /etc/ceph/ceph.client.crash.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) WARNING:ceph-crash:post /var/lib/ceph/crash/2025-08-21T10:28:14.730789Z_ad2ef583-85b7-4cf0-a2fd-2fa3b775a7a2 as client.admin failed: 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 AuthRegistry(0x7fa800064068) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 AuthRegistry(0x7fa800068540) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 auth: unable to find a keyring on /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin: (2) No such file or directory 2025-08-22T06:55:50.726+0000 7fa805ea96c0 -1 AuthRegistry(0x7fa805ea8410) no keyring found at /etc/ceph/ceph.client.admin.keyring,/etc/ceph/ceph.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin, disabling cephx [errno 2] RADOS object not found (error connecting to the cluster) ...... In /etc/ceph I have ceph.client.admin.keyring ceph.conf rbdmap Maye there is a way to fix this but if it's to complicated I will think about a complete re-install. I'm not an admin but an amateur with some linux knowledge. If there is hope and someone could support to solev this I would be very happy! Regards, Christian Peters

3 7

smartctl failed with error -22
by Robert Sander 22 Aug '25

22 Aug '25

Hi, On a new cluster with version 19.2.3 the device health metrics only show a smartctl error: { "20250821-000313": { "dev": "/dev/sdc", "error": "smartctl failed", "nvme_smart_health_information_add_log_error": "nvme returned an error: sudo: exit status: 1", "nvme_smart_health_information_add_log_error_code": -22, "nvme_vendor": "ata", "smartctl_error_code": -22, "smartctl_output": "smartctl returned an error (1): stderr:\nsudo: exit status: 1\nstdout:\n" } } The device in question (like all the other in the cluster) is a Samsung MZ7L37T6 SATA SSD. What is happening here? Regards -- Robert Sander Linux Consultant Heinlein Consulting GmbH Schwedter Str. 8/9b, 10119 Berlin https://www.heinlein-support.de Tel: +49 30 405051 - 0 Fax: +49 30 405051 - 19 Amtsgericht Berlin-Charlottenburg - HRB 220009 B Geschäftsführer: Peer Heinlein - Sitz: Berlin

5 8

[v19.2.3] All OSDs are not created with a managed spec
by Gilles Mocellin 22 Aug '25

22 Aug '25

On Hi Cephers, I'm building a new Squid cluster with cephadm on Ubuntu 24.04. After expanding my cluster in the Dashboard (adding my 7 hosts), I choose throughput_optimized proflie wich create a generic spec for hybrid HDD/SSD : service_type: osd service_id: throughput_optimized service_name: osd.throughput_optimized placement: host_pattern: '*' spec: data_devices: rotational: 1 db_devices: rotational: 0 encrypted: true filter_logic: AND objectstore: bluestore The cluster is for a LAB environment, on each of the 7 nodes, I have 17 HDD SAS 1.2TB drives and 1 SSD SAS Enterprise 400GB drive. On my first try, only 28 OSD where created (out of the 119), the others appeared as down, but they won't start, I didn't find systemd units created on the hosts. But, the VGs and LVs where created, there are 17 LVs on the SSD for WAL/DB of the 17 HDD (yes, small : 29GB). On my second try, it creates 72 OSDs, still it stops, and never tries to continue, or re-create the down OSDs. I didn't manage to find them, but it seems I saw some OSD creation timeout in the logs... What can I do to have my missing OSD created ? I tried restarting, redeploying the orch OSD service, but it only restart/redeploy le OSDs it has already created...

6 17

[v19.2.3] Zapped OSD are not recreated with DB device
by Gilles Mocellin 22 Aug '25

22 Aug '25

Hi, Having timeout problems with my cluster, I try to finsh, recreate OSDs that failed. My config is hybrid with 17 HDD and 1 SSD by server. My OSD spec is the standard : service_type: osd service_id: throughput_optimized service_name: osd.throughput_optimized placement: host_pattern: '*' spec: data_devices: rotational: 1 db_devices: rotational: 0 objectstore: bluestore encrypted: true filter_logic: AND When I remove an OSD with : ceph orch osd rm ID --zap It is finaly re-created, but without DB device. And I can see the ceph-volume commands : Zapping : cephadm ['--image', 'quay.io/ceph/ceph@sha256:7c69e59beaeea61ca714e71cb84ff6d5e533db7f1fd84143dd9ba6649a5fd2ec', '--timeout', '2395', 'ceph-volume', '--fsid', '8ec7575a-7de5-11f0-a78a-246e96bd90a4', '--', 'lvm', 'zap', '--osd-id', '82', '--destroy'] Recreate : cephadm ['--env', 'CEPH_VOLUME_OSDSPEC_AFFINITY=throughput_optimized', '--image', 'quay.io/ceph/ceph@sha256:7c69e59beaeea61ca714e71cb84ff6d5e533db7f1fd84143dd9ba6649a5fd2ec', '--timeout', '2395', 'ceph-volume', '--fsid', '8ec7575a-7de5-11f0-a78a-246e96bd90a4', '--config-json', '-', '--', 'lvm', 'batch', '--no-auto', '/dev/sde', '--dmcrypt', '--osd-ids', '82', '--yes', '--no-systemd'] I think it should have the argument --db-devices ? I can see that option when the OSD spec was applied, it launch for all drives on the host : cephadm ['--env', 'CEPH_VOLUME_OSDSPEC_AFFINITY=throughput_optimized', '--image', 'quay.io/ceph/ceph@sha256:7c69e59beaeea61ca714e71cb84ff6d5e533db7f1fd84143dd9ba6649a5fd2ec', '--timeout', '2395', 'ceph-volume', '--fsid', '8ec7575a-7de5-11f0-a78a-246e96bd90a4', '--config-json', '-', '--', 'lvm', 'batch', '--no-auto', '/dev/sda', '/dev/sdb', '/dev/sdc', '/dev/sdd', '/dev/sde', '/dev/sdf', '/dev/sdg', '/dev/sdh', '/dev/sdi', '/dev/sdj', '/dev/sdk', '/dev/sdl', '/dev/sdm', '/dev/sdn', '/dev/sdo', '/dev/sdp', '/dev/sdq', '--db-devices', '/dev/sdr', '--dmcrypt', '--yes', '--no-systemd'] There is the --db-devices argument. Is it a bug or I do it wrong ? I have several OSD that are now without DB device, I want to recreate them with the DB device. And also, I want that every time a new drive is created, it will be with a DB device, or fails if no room, but not create without DB device if my OSD SPEC tells it.

2 5

Re: Disk failure (with osds failure) cause 'unrelated|different' osd device to crash
by Wissem MIMOUNA - Ceph Users 21 Aug '25

21 Aug '25

Hi , The issue here is that one nvme failed so related osds ( let's say osd.1 , osd.2 , osd.3 and osd.4 ) all crashes and in the meantime another osd ( osd.108 ) on the same host crashes too (2 times with 2 different failed nvme ) on the same assert_line and assert_file as below ) . So why this happened just one the nvme failed? Is they are related ? I can,'t have a clear vue ... Regards On 8/21/25 15:57, Anthony D'Atri wrote: > >> We had a ceph cluster version 18.2.7 deployed with four osds per nvme device. > Post-Quincy the benefits of multiple OSDs per NVMe device are mostly obviated. > > Or are you saying that you have HDD OSDs that offload WAL+DB? > >> Two weeks ago, we lost one hard drive ( so 4 osds ) , just after the osds had crashed , we had another "healthy" osd which crashed ( few minutes after the initial hard drive failure ) . >> >> Again , this week we lost another hard drive ( lost 4 osds ) and again the same osd crashed too ( few minutes later ) . >> >> Here below the crash information , the same crash information for both crashes : >> >> >> ceph crash info 2025-08-21T00:31:13.929426Z_576e6e42-7c6b-49b8-90f1-9d51730f8ac2 >> { >> "assert_condition": "r == 0", >> "assert_file": "/home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos9/DIST/centos9/MACHINE_SIZE/gigantic/release/18.2.7/rpm/el9/BUILD/ceph-18.2.7/src/os/bluestore/BlueStore.cc", >> "assert_func": "void BlueStore::_txc_apply_kv(BlueStore::TransContext*, bool)", >> "assert_line": 12944, >> "assert_msg": "/home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos9/DIST/centos9/MACHINE_SIZE/gigantic/release/18.2.7/rpm/el9/BUILD/ceph-18.2.7/src/os/bluestore/BlueStore.cc: In function 'void BlueStore::_txc_apply_kv(BlueStore::TransContext*, bool)' thread 7f5fba6a3640 time 2025-08-21T00:31:13.926894+0000\n/home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos9/DIST/centos9/MACHINE_SIZE/gigantic/release/18.2.7/rpm/el9/BUILD/ceph-18.2.7/src/os/bluestore/BlueStore.cc: 12944: FAILED ceph_assert(r == 0)\n", >> "assert_thread_name": "bstore_kv_sync", >> "backtrace": [ >> "/lib64/libc.so.6(+0x3ebf0) [0x7f5fce5a5bf0]", >> "/lib64/libc.so.6(+0x8bf5c) [0x7f5fce5f2f5c]", >> "raise()", >> "abort()", >> "(ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x169) [0x560bc2d0e44d]", >> "/usr/bin/ceph-osd(+0x3cc5ae) [0x560bc2d0e5ae]", >> "/usr/bin/ceph-osd(+0x3b8864) [0x560bc2cfa864]", >> "(BlueStore::_kv_sync_thread()+0x1073) [0x560bc32bb623]", >> "/usr/bin/ceph-osd(+0x8fd3b1) [0x560bc323f3b1]", >> "/lib64/libc.so.6(+0x8a21a) [0x7f5fce5f121a]", >> "/lib64/libc.so.6(+0x10f290) [0x7f5fce676290]" >> ], >> "ceph_version": "18.2.7", >> "crash_id": "2025-08-21T00:31:13.929426Z_576e6e42-7c6b-49b8-90f1-9d51730f8ac2", >> "entity_name": "osd.108", >> "os_id": "centos", >> "os_name": "CentOS Stream", >> "os_version": "9", >> "os_version_id": "9", >> "process_name": "ceph-osd", >> "stack_sig": "0080731b49e5583e6d168903c1ea7df8bc2caded6b5e24ee4381077d54b045e2", >> "timestamp": "2025-08-21T00:31:13.929426Z", >> "utsname_hostname": "pub1-cephosd-9", >> "utsname_machine": "x86_64", >> "utsname_release": "6.1.0-31-amd64", >> "utsname_sysname": "Linux", >> "utsname_version": "#1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07)" >> >> >> Regards >> _______________________________________________ >> ceph-users mailing list -- ceph-users(a)ceph.io >> To unsubscribe send an email to ceph-users-leave(a)ceph.io

1 0

Disk failure (with osds failure) cause 'unrelated|different' osd device to crash
by Wissem MIMOUNA - Ceph Users 21 Aug '25

21 Aug '25

Hi everyone , We had a ceph cluster version 18.2.7 deployed with four osds per nvme device. Two weeks ago, we lost one hard drive ( so 4 osds ) , just after the osds had crashed , we had another "healthy" osd which crashed ( few minutes after the initial hard drive failure ) . Again , this week we lost another hard drive ( lost 4 osds ) and again the same osd crashed too ( few minutes later ) . Here below the crash information , the same crash information for both crashes : ceph crash info 2025-08-21T00:31:13.929426Z_576e6e42-7c6b-49b8-90f1-9d51730f8ac2 { "assert_condition": "r == 0", "assert_file": "/home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos9/DIST/centos9/MACHINE_SIZE/gigantic/release/18.2.7/rpm/el9/BUILD/ceph-18.2.7/src/os/bluestore/BlueStore.cc", "assert_func": "void BlueStore::_txc_apply_kv(BlueStore::TransContext*, bool)", "assert_line": 12944, "assert_msg": "/home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos9/DIST/centos9/MACHINE_SIZE/gigantic/release/18.2.7/rpm/el9/BUILD/ceph-18.2.7/src/os/bluestore/BlueStore.cc: In function 'void BlueStore::_txc_apply_kv(BlueStore::TransContext*, bool)' thread 7f5fba6a3640 time 2025-08-21T00:31:13.926894+0000\n/home/jenkins-build/build/workspace/ceph-build/ARCH/x86_64/AVAILABLE_ARCH/x86_64/AVAILABLE_DIST/centos9/DIST/centos9/MACHINE_SIZE/gigantic/release/18.2.7/rpm/el9/BUILD/ceph-18.2.7/src/os/bluestore/BlueStore.cc: 12944: FAILED ceph_assert(r == 0)\n", "assert_thread_name": "bstore_kv_sync", "backtrace": [ "/lib64/libc.so.6(+0x3ebf0) [0x7f5fce5a5bf0]", "/lib64/libc.so.6(+0x8bf5c) [0x7f5fce5f2f5c]", "raise()", "abort()", "(ceph::__ceph_assert_fail(char const*, char const*, int, char const*)+0x169) [0x560bc2d0e44d]", "/usr/bin/ceph-osd(+0x3cc5ae) [0x560bc2d0e5ae]", "/usr/bin/ceph-osd(+0x3b8864) [0x560bc2cfa864]", "(BlueStore::_kv_sync_thread()+0x1073) [0x560bc32bb623]", "/usr/bin/ceph-osd(+0x8fd3b1) [0x560bc323f3b1]", "/lib64/libc.so.6(+0x8a21a) [0x7f5fce5f121a]", "/lib64/libc.so.6(+0x10f290) [0x7f5fce676290]" ], "ceph_version": "18.2.7", "crash_id": "2025-08-21T00:31:13.929426Z_576e6e42-7c6b-49b8-90f1-9d51730f8ac2", "entity_name": "osd.108", "os_id": "centos", "os_name": "CentOS Stream", "os_version": "9", "os_version_id": "9", "process_name": "ceph-osd", "stack_sig": "0080731b49e5583e6d168903c1ea7df8bc2caded6b5e24ee4381077d54b045e2", "timestamp": "2025-08-21T00:31:13.929426Z", "utsname_hostname": "pub1-cephosd-9", "utsname_machine": "x86_64", "utsname_release": "6.1.0-31-amd64", "utsname_sysname": "Linux", "utsname_version": "#1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07)" Regards

1 0