LinearTapeFileSystem / LinearTapeFileSystem/ltfs
PR key as option?
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 352
- Forks
- 110
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 2
Description
We are trying to run LTFS in k8s pod, the IP of pod changes once the pod is recreated. The problem we hit is, when a POD is not stopped gracefully such as the node that running the POD hit a power outage, when this node is power back on, the LTFS that running in the recreated POD can not mount the tape, because the persistent reservation that placed by previous POD is IPv4 address of previous POD.
If we can pass key as command line option or an env var such as "LTFS_SG_PR_KEY", we can obtain the IP of node via downward API of k8s, so that we can mount the same tape in the same drive as previous POD since we have the same PR key as the one set in previous mount.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing where LTFS sets the persistent-reservation key during tape mounting and how command-line options or environment variables are parsed. Done means a caller can provide the key through the proposed option or LTFS_SG_PR_KEY and a recreated Kubernetes pod can mount the same tape and drive with that key.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100