Snapper over dm-crypt volume
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 1.2k
- Forks
- 160
- Avg merge
- 5d 18h
- Merged PRs (30d)
- 3
Description
Hi,
I'd like to know if there would be a way to use snapper over a dm-crypt volume (on top of LVM).
I have a thin-provisionned LVM, on top of which I put a luks volume, on top of which I have an ext4 filesystem.
I understand it would be complex to have diff and commands such as this. What I'm mostly interested is in the snaphot and expiry. I could do it myself in a shell script obviously, but I thought it would be nice to be able to do this through snapper, as all other thin volumes are done by snapper on this machine.
Something like having a lvm(raw) option, to tell snapper to only manage the lvm-thin layer and don't bother with trying to be smart with what's in it. snapper would then only do the housekeeping of these snapshots.
Regards
Contributor guide
No contributing guide indexed for this repository
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 reviewing how snapper currently handles LVM thin volumes and its snapshot expiry workflow. Define the scope for managing only the LVM-thin layer over a dm-crypt/LUKS volume, with snapshot creation and housekeeping but no filesystem-level diff or related commands; done means that behavior is supported and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100