I posted in a previous thread about how I had an issue with my ceph configuration and purged ceph. I managed to get it reinstalled and I have the mons/mgrs setup but when I go to create a pool, I receive this message:
I also intermittently get
Any ideas?
EDIT:
In case anyone finds this thread, it was actually because my host OS disk was too slow. The slow storage was the cause of both timeouts and issues with pool creation.
I didn't properly read the requirements and recommendations and was running this on the Dell ISDDM SD cards built-in my M620 and M630 servers. The read/write is too slow and offers a limited lifespan. Opted instead to install Proxmox on one of the two SSDs on each host.
After installation on capable hardware, everything just works!
Code:
pool pool01: applying size = 3
got timeout
pool pool01: applying application = rbd
syswrite() on closed filehandle $child at /usr/share/perl5/PVE/RADOS.pm line 34.
write data failed - Bad file descriptor
pool pool01: applying crush_rule = replicated_rule
syswrite() on closed filehandle $child at /usr/share/perl5/PVE/RADOS.pm line 34.
write data failed - Bad file descriptor
pool pool01: applying min_size = 2
syswrite() on closed filehandle $child at /usr/share/perl5/PVE/RADOS.pm line 34.
write data failed - Bad file descriptor
pool pool01: applying pg_autoscale_mode = on
syswrite() on closed filehandle $child at /usr/share/perl5/PVE/RADOS.pm line 34.
write data failed - Bad file descriptor
pool pool01: applying pg_num = 128
syswrite() on closed filehandle $child at /usr/share/perl5/PVE/RADOS.pm line 34.
write data failed - Bad file descriptor
pool pool01: applying target_size_bytes = 0
syswrite() on closed filehandle $child at /usr/share/perl5/PVE/RADOS.pm line 34.
write data failed - Bad file descriptor
TASK ERROR: Could not set: application, crush_rule, min_size, pg_autoscale_mode, pg_num, size, target_size_bytes
I also intermittently get
got timeout (500)
errors. I think they may be from clock skew according to journalctl -u ceph-mon@host
, so I've applied changes to my chrony.conf to remedy that (hopefully).Any ideas?
EDIT:
In case anyone finds this thread, it was actually because my host OS disk was too slow. The slow storage was the cause of both timeouts and issues with pool creation.
I didn't properly read the requirements and recommendations and was running this on the Dell ISDDM SD cards built-in my M620 and M630 servers. The read/write is too slow and offers a limited lifespan. Opted instead to install Proxmox on one of the two SSDs on each host.
After installation on capable hardware, everything just works!
Last edited: