Can Garage work with NFS-backed storage? #986
Labels
No labels
action
check-aws
action
discussion-needed
action
for-external-contributors
action
for-newcomers
action
more-info-needed
action
need-funding
action
triage-required
kind
correctness
kind/experimental
kind
ideas
kind
improvement
kind
performance
kind
testing
kind
usability
kind
wrong-behavior
prio
critical
prio
low
scope
admin-api
scope
admin-sdk
scope
background-healing
scope
build
scope
documentation
scope
k8s
scope
layout
scope
metadata
scope
ops
scope
rpc
scope
s3-api
scope
security
scope
telemetry
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Deuxfleurs/garage#986
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I’m interested in deploying Garage with an NFS-backed storage setup. I’d like to know if Garage supports running on top of NFS-mounted directories or if there are any known issues or limitations with this configuration.
Fundamentally it should be possible, as garage doesn't really do anything fancy with the underlying file system. At least for the data folder. For the metadata, things could be more tricky depending on the backend used. In any cases this would likely not be something we would spend time supporting. What's your use-case?
We have a few use cases and challenges, both technical and organizational.
As a storage backend, what prevents you from hosting garage on the NAS itself or though something like iSCSI?
The main challenges preventing us from hosting Garage directly on the NAS or using iSCSI are:
My goal is to:
In my prior setup, I was running META locally (because you need something FAST you have no other solution) and /data into a NFS Share.
I worked like a charm. (On home setup).