Search results

Big Than You to @RokaKen ! This issue is solved now: Swapping/changing to new SSDs made the ssd-pool responsive again The correction of the crush rules and the correct assignment to the respective pools enabled the full potential of the NVMe

{ "mon": { "ceph version 16.2.6 (1a6b9a05546f335eeeddb460fdc89caadf80ac7a) pacific (stable)": 3 }, "mgr": { "ceph version 16.2.6 (1a6b9a05546f335eeeddb460fdc89caadf80ac7a) pacific (stable)": 3 }, "osd": { "ceph version 16.2.6...

Hi @aaron , ceph osd pool autoscale-status runs without any output.

As per $HISTFILE the manual CRUSH rule for the SSD class was presumedly built by ceph osd crush rule create-replicated repl-ssd default host ssd. So this basically means, I create another CRUSH rule like so: ceph osd crush rule create-replicated repl-nvme default host nvme? And then edit the...

So thanks a ton @RokaKen - this helps me to understand this issue and to link the clearly bad performing SSD to the issue with the NVMe pool (which apparently is not NVMe only)! Will start by changing the suspected bad/faulty SSD. Yes, the plan was to have strictly separated pools for the...

Hi, @RokaKen , here it is: root@pve-node-01:~# ceph osd pool ls detail pool 1 'device_health_metrics' replicated size 3 min_size 2 crush_rule 0 object_hash rjenkins pg_num 512 pgp_num 512 autoscale_mode on last_change 3612 lfor 0/0/73 flags hashpspool stripe_width 0 pg_num_min 1 application...

Hi, I am Hans, I am using Proxmox for quite some time now and often found valuable help (reading) this community. Thanks a lot for so much valuable information! Today I have some questions which I could not help myself, so I am posting my 1st post :-) I recently inherited a 3 node...