Channels
cluster-api
extensions
rancher-extensions
sle
sle-bci
harvester-dev
neuvector-security
supermicro-sixsq
onlinetraining
office-hours
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
espanol
lima
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
rancher-setup
developer
mexico
random
elemental
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
s3gw
hobbyfarm
rancher-desktop
general
rke2
Powered by
#longhorn-storage
Title
# longhorn-storage
f
famous-journalist-11332
07/26/2022, 12:53 AM
Yeah, it could be normal. Can you see if this document clear up the confusion?
https://longhorn.io/docs/1.3.0/volumes-and-nodes/volume-size/
f
flaky-coat-75909
07/26/2022, 7:09 AM
@famous-journalist-11332
if it is normal It is fine I will deep dive in this link I have one request can you look up on my second question?
https://rancher-users.slack.com/archives/CC2UQM49Y/p1658263742990219?thread_ts=1658223767.108449&cid=CC2UQM49Y
and if you can answer it would be great 🙂
Post