Feature request: Confirm mounting of remote locations or automount
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- operating-systems
Research direction
The issue names no files, tests, or entry points. Start by mapping how Timeshift selects and verifies snapshot locations, then investigate the proposed remote automount and empty-mount-folder marker alternatives. Done would require an agreed approach for unavailable remote locations, safe mounting behavior, and failure notification.
Written by the indexing model from the issue text.
Description
I've been setting up to backup to a remote location rather than keep timeshift data locally. The main headache is if that remote location isn't available for some reason, in which case the timeshift data winds up dumping to the empty mount folder, using up space on the local drive for no good reason.
Ideally, timeshift really needs to integrate remote access just like gui file shares, being able to save to something like: smb://[email protected]/backup/this_machine and have timeshift automount to a temporary folder and unmount when it's done, sending a notification if something fails. This wouldn't be trivial, unfortunately.
You could workaround by placing a marker file in the empty mount folder telling timeshift to halt and notify there was an error if this file was found. The file would be hidden by the remote location whenever it was properly mounted. This would be a bit annoying to put in place and would require more knowledge of how mounting remote locations works.
- Dominant language
- Vala
- Stars
- 4.3k
- Forks
- 158
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from linuxmint/timeshift
-
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 74/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in linuxmint/timeshift
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
riscv-software-src/riscv-isa-sim#2466 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
area:runtime bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
crmne/zapfast#446 · 1 comment · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
ChrisTitusTech/winutil#5145 ·
Maintainers usually reply within 6 days