This message was deleted.
# longhorn-storage
a
This message was deleted.
f
In diffrent pvc I have 2dir
Copy code
1.6G	pvc-88c89178-d3ae-41d5-92bb-0dc3f30350b8-523c9fbc
17G	pvc-88c89178-d3ae-41d5-92bb-0dc3f30350b8-e1824848
and
Copy code
12G	pvc-39e0dc39-f3ec-43f7-b518-3bf2d58de4a1-8d845516
1.6G	pvc-39e0dc39-f3ec-43f7-b518-3bf2d58de4a1-10dd68f1
is it normal?
l
What version of Longhorn?
Version of Kubernetes?
f
Longhorn version =
v1.3.0
k8s version -=
Major:"1", Minor:"23"
@late-needle-80860
l
What’s the full path to these pvc’s?
f
/docker/lib/longhorn/replicas/pvc-48586aa6-cc79-40e0-94b1-bf20e48ffa72-01eb5a76
where path
Path: /docker/lib/longhorn/
was added as a disk
the rest of those volume have prefix
/docker/lib/longhorn/replicas/NAME_OF_PVC+SUFFIX
l
So I think you should use a dedicated storage space for Longhorn and not what seems to be the sys disk
Also why are you still using the docker container runtime?
f
the /docker is dedicated storage space mayby the name
docker
is confusing
Also why are you still using the docker container runtime?
which should I use instead of docker?
l
What Kubernetes flavor are you on? K0s, K3s or something third?
It’s totally confusing that
docker
is part of the folder name.
f
k8s installed via kubeadm
👍 1
l
Use
containerd
… the docker shim have been deprecated in newer version of Kubernetes for some time.
But, the replicas there are to be expected. The default conf. setting of Longhorn is to have 3 replicas per PVC
f
ah, and even If I have single node it will create 3 x replicated directorieries on single node?
l
You can control the default in the storage class backing your pvcs …
numberOfReplicas
is what you’re looking for
n