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

Hard links and sparse files #13

Closed
andrewchambers opened this issue Sep 7, 2022 · 3 comments
Closed

Hard links and sparse files #13

andrewchambers opened this issue Sep 7, 2022 · 3 comments

Comments

@andrewchambers
Copy link
Contributor

Bupstash supports these, I don't know about the other tools.

@deajan
Copy link
Owner

deajan commented Sep 7, 2022

I need to understand before adding this to the comparaison table:

  • hardlinks
    • does bupstash have an option to explicitly avoid or follow them ? (Did a quick search on bupstash.io, didn't find any doc)
  • sparse files
    • does bupstash know which files are sparse files, so it will not actually try to compress / dedup the empty part of the file ?

@andrewchambers
Copy link
Contributor Author

I think you are confusing hardlinks and symlinks. On linux you create a hardlink with ln and a symlink with ln -s. A hard link looks as if they are a normal file but actually both point to the same inode on the filesystem.

I mainly mean if you backup a filesystem that has hardlinks and sparse files does the backup tool preserve and restore them or discard that information. It can be quite important this information is not lost. As an example if sparse file information is not restored properly you can run out of disk space when trying to restore files that previously fit on a disk.

@deajan
Copy link
Owner

deajan commented Oct 2, 2022

Indeed, read too fast for the hardlinks. I've updated the comparaison with your requests. Thanks.

@deajan deajan closed this as completed Oct 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants