On 2020-12-01 13:19, Oliver Weinmann wrote:
>
> podman ps -a didn't show that container. So I googled and stumbled over
> this post:
>
> https://github.com/containers/podman/issues/2553
>
> I was able to fix it by running:
>
> podman rm --storage
> e43f8533d6418267d7e6f3a408a566b4221df4fb51b13
Yes, I deployed via cephadm on CentOS 7, it is using podman. The
container doesn't even start up so I don't get a container id. But i
checked journalctl -xe, and it seems that its trying to use a container
name that still exists.
-- Unit ceph-d0920c36-2368-11eb-a5de-005056b703af@osd.0.service
On 2020-12-01 10:21, Oliver Weinmann wrote:
> Hi Stefan,
>
> unfortunately It doesn't start.
>
> The failed osd (osd.0) is located on gedaopl02
>
> I can start the service but then after a minute or so it fails. Maybe
> I'm looking at the wrong log file, but it's empty:
Maybe it hits a timeout
Hi Stefan,
unfortunately It doesn't start.
The failed osd (osd.0) is located on gedaopl02
[root@gedasvl02 ~]# ceph osd tree
INFO:cephadm:Inferring fsid d0920c36-2368-11eb-a5de-005056b703af
INFO:cephadm:Inferring config
/var/lib/ceph/d0920c36-2368-11eb-a5de-005056b703af/mon.gedasvl02/config
IN
On 2020-11-30 15:55, Oliver Weinmann wrote:
> I have another error "pgs undersized", maybe this is also causing trouble?
This is a result of the loss of one OSD, and the PGs located on it. As
you only have 1 OSDs left, the cluster cannot recover on a third OSD
(assuming defaults here). The cluste
