Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

could rsbackup have a mollyguard check that device-id is actually at the root of a filesystem? #42

Closed
pm215 opened this issue Jan 26, 2018 · 1 comment

Comments

@pm215
Copy link

@pm215 pm215 commented Jan 26, 2018

Hi; this is a wishlist suggestion based on a user error I made this week bringing a new backup disk into service. Basically when I created the "device-id" file I forgot to actually mount the backup disk first. The result was that rsbackup happily started to back the machine's root disk up to a subdirectory of itself, until it ran out of disk space.

Would it be possible/sensible for rsbackup to complain if the directory with device-id isn't actually a filesystem root? (I guess you'd want an override for people doing odd things, but the 99% usecase is presumably that it should be the fs root.)

@ewxrjk
Copy link
Owner

@ewxrjk ewxrjk commented Jan 26, 2018

Yes, I think this is a good idea.

@ewxrjk ewxrjk added this to the 6.0 milestone Jan 27, 2018
ewxrjk added a commit that referenced this issue Feb 16, 2018
--store now has the same behavior as the 'store' directive: the store
must be a mount point. --unmounted-store allows store directories
that aren't mount points. As well as providing an escape hatch to the
previous behavior we need this for testing.

re #42
@ewxrjk ewxrjk closed this in 2f32dd5 Feb 16, 2018
ewxrjk added a commit that referenced this issue Jul 27, 2018
This can be disabled with new options to store and store-pattern.

fixes #42
ewxrjk added a commit that referenced this issue Jul 27, 2018
--store now has the same behavior as the 'store' directive: the store
must be a mount point. --unmounted-store allows store directories
that aren't mount points. As well as providing an escape hatch to the
previous behavior we need this for testing.

re #42
@ewxrjk ewxrjk modified the milestones: 6.0, 5.1 Jul 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants