Search results

I have to say, that I also found this documentation and I did set bluestore_slow_ops_warn_threshold per problematic OSD and warning is gone ! So it is really seems to be a feature ....

Anyone tried this ? https://github.com/rook/rook/discussions/15403 Specially this two: ceph config set global bdev_async_discard_threads 1 ceph config set global bdev_enable_discard true

I am not able to do snapshots on RBD storage, another bug: https://tracker.ceph.com/issues/61582?next_issue_id=61581 I have had using Ceph long time, but, this going to be worse and worse ...

I have upgraded too to 19.2.2 before weekend, but no luck: HEALTH_WARN: 2 OSD(s) experiencing slow operations in BlueStore osd.9 observed slow operation indications in BlueStore osd.15 observed slow operation indications in BlueStore

wuwzy: You were right, from time to time, osd is slow... clean itself ... come again ... , etc ...

A still have no alerts for 5 days ...

Hi all, I am just observing and witing for a real patch, I have did not "repair" CEPH health anyhow, but .... All warnings did disappeared a 3-4 days ago and CEPH health is green ... So I am confused ... :-)

root@pve1:~# pveceph pool get cephfs_data ┌────────────────────────┬─────────────────┐ │ key │ value │ ╞════════════════════════╪═════════════════╡ │ crush_rule │ replicated_rule │ ├────────────────────────┼─────────────────┤ │ fast_read │ 0...

?

Ceph bug ? https://github.com/rook/rook/discussions/15403

Hi, guys same issue here after upgrade to CEPH 19.2.1... Environment 3 nodes: proxmox-ve: 8.4.0 (running kernel: 6.8.12-9-pve) pve-manager: 8.4.1 ceph: 19.2.1-pve3 HEALTH_WARN: 2 OSD(s) experiencing slow operations in BlueStore osd.9 observed slow operation indications in BlueStore osd.15...

This post should NOT to be solved ... in my opinion ...

Uff, so It was good idea NOT to recreate storage .... I am watching this: https://tracker.ceph.com/issues/61582?next_issue_id=61581 And I seems that nobody cares ... I suppose that combination LXC + CEPH has no many "users" ..... I also had big troubles with LXC and nfs mount under...

Hi, I have exact the same problem. After 3 months I do not see any progress here: https://tracker.ceph.com/issues/61582?next_issue_id=61581 So I suppose this issue is not solved, Am I right ? Thanks for the reply. :) PS: I have empty cephfs on my pool. but I am scared to delete it.

This is the way :)

OK. To be more specific, we use for example 4210, which is the same "Cascade Lake " like your 4215 ... Ok. Thanks for the info ...

Hi all, we have many PVE servers. Recently I have upgraded all of them to latest PVE 7.2.4, 7.2.5 among with the latest kernel 5.15. All the servers have Xeon(R) Silver 41XX processors, and we have NO issue with VM destroy mentioned here. Servers are mostly Supermicro or HP. But we also have...

Pinning kernel: proxmox-boot-tool kernel pin 5.13.19-6-pve Did not force the kernel 5.13.19-6-pve to be booted first .. So check, If you REALY run this kernel after reboot ...

Yes: " is to keep a close eye on them" this is exactly what i do NOT want to do :). Because if more admins take care about the pool, they always must have on their minds: I must count what is full provisioned, when I want to make a new VM, or expand the disk for a some VM. And when after login...

Hello, can anybody from proxmox answer ? Thanks a lot ...