Burn1ngBull3t
@Burn1ngBull3t@lemmy.world
- Submitted 3 months ago to selfhosted@lemmy.world | 3 comments
- Comment on [K8S] nfs and mounting problems 7 months ago:
Hello @theit8514
You are actually spot on ^^
I did look in my exports file which was like so :
/mnt/DiskArray 192.168.0.16(rw) 192.168.0.65(rw)I added a localhost line in case:
/mnt/DiskArray 127.0.0.1(rw) 192.168.0.16(rw) 192.168.0.65(rw)It didn’t solve the problem. I went to investigate with the mount command:
-
Will mount on 192.168.0.65:
mount -t nfs 192.168.0.55:/mnt/DiskArray/mystuff/ /tmp/test -
Will NOT mount on 192.168.0.55 (NAS):
mount -t nfs 192.168.0.55:/mnt/DiskArray/mystuff/ /tmp/test -
Will mount on 192.168.0.55 (NAS):
mount -t nfs 127.0.0.1:/mnt/DiskArray/mystuff/ /tmp/test
The
mount -t nfs 192.168.0.55is the one that the cluster does actually. So i either need to find a way for it to use 127.0.0.1 on the NAS machine, or use a hostname that might be better to resolve -
- Submitted 7 months ago to selfhosted@lemmy.world | 3 comments
- Comment on Longhorn overkill for RAID ? 9 months ago:
Exactly thanks!
- Comment on Longhorn overkill for RAID ? 9 months ago:
Haha sorry indeed, it’s Kubernetes related and not Windows WeDontSayItsName related 😄
- Comment on Longhorn overkill for RAID ? 9 months ago:
You are completely right.
However in my mind (might be wrong here) if I use another node, i wouldn’t use the RAID array completely.
While setup up i thought that its either:
- NAS storageClass attached to the RAID array, no longhorn
- with longhorn when there is no RAID, but replication at 3
In either case, the availability of my data would be quite the same right ?
(Then there is options to backup my PV to s3 with longhorn and all that i would have to setup again though )
Thanks for your answer !
- Comment on Longhorn overkill for RAID ? 9 months ago:
Hello ! Thanks for your response!
Yes RAID is used as availability of my data here, with or without longhorn, there wouldn’t be much difference there (especially since i only use one specific node)
And you would be right, since the other nodes are unscheduled, it will be available only on my “storage node” so if this one goes down my storage goes down.
That’s why i might be overkill with longhorn, but there are functions to restore and backup to s3 for exemple that i would need to setup i guess
- Submitted 9 months ago to selfhosted@lemmy.world | 11 comments
- Comment on Questions on backing up to S3 Glacier Deep Archive. 10 months ago:
Hello ! Just adding my two cents for Scaleway. I’ve used them personally for some services (and probably will add s3 storage in the near future)
It’s seems pretty reliable in my opinion.
- Comment on Most of the things I do are inspired by things that frightened me when I was young. 11 months ago:
Still from IT Crowd, it’s when Reynholm get sued by his exwife. The quote isn’t from that episode though
- Comment on Best usage of motherboard 11 months ago:
I think you are right indeed, i had the idea to maybe use the GC for AI stuff and play with it. I would probably go with kube and add the NAS in longhorn (that i already set up)
- Comment on Best usage of motherboard 11 months ago:
Would have been cool to add yet another machine to the cluster, especially if i could use the NAS for the kube VolumeClaims. 🤔
- Comment on Best usage of motherboard 11 months ago:
Also true
- Submitted 11 months ago to selfhosted@lemmy.world | 10 comments