-
-
Notifications
You must be signed in to change notification settings - Fork 502
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
DietPi-Backup | Sync RootFS from temporary mount point #2558
Comments
Not as simple as one might think: https://dietpi.com/phpbb/viewtopic.php?p=18437#p18437 Probably best:
|
I'll mark this as closed. We have a more flexible implementation which gives more power to the user: Also the original idea to sync from a temporary root filesystem mount doesn't make sense as of the above mentioned points that other filesystems may contain important system files as well, most notably the |
Just derived that method from: https://github.com/raspberrypi-ui/piclone/blob/master/src/backup
I didn't know that mounting the same drive/partition to two mount points is possible.
df
does not show the second mount point, but one can access it.Mounting RootFS to a temporary mount point has the advantage that only the actual partitions content is synced, not the content of kernel or user mounts, like
/proc
/sys
/dev
/run
/tmp
and/mnt/*
. So we don't need to exclude them manually.As well this allows to clean tmpfs mount points, if somehow content was created on the actual drive there. I was always annoyed by boot messages like "
/tmp mount point is not empty, mounting anyway
" and alike 😉. And my/dev
and/run
had some content as well, however this happened 😄./boot
should be mounted and backed up as well, but everything else should be skipped anyway?The text was updated successfully, but these errors were encountered: