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

Define and implement behaviour for hardlinks #2

Open
jotaen opened this issue Jan 22, 2024 · 1 comment
Open

Define and implement behaviour for hardlinks #2

jotaen opened this issue Jan 22, 2024 · 1 comment

Comments

@jotaen
Copy link
Owner

jotaen commented Jan 22, 2024

I also haven’t considered hardlinks so far, so their behaviour is not well-defined.

Hardlinks are quite tricky, because their behaviour depends on how the snapshots were created, or whether you compare two snapshots against each other, or whether you compare one snapshot against the original directory tree.

  • If you do cp -R for creating a snapshot, then all hardlinks from the original directory tree are created as individual files in the snapshot.
  • If you do rsync -r --hard-links for creating a snapshot, then all hardlinks from the original directory tree are cloned (as hardlinks) in the snapshot.

The other issue is that it’s more complex to determine the “redundant” hardlinks within the same snapshot in the first place.

Not sure yet, what the best solution is here. I’m also not sure how common this problem actually is, or whether the additional complexity of solving it is worth the benefit.

@jotaen jotaen changed the title Look into hardlink/symlink handling Define (and implement) behaviour for hardlinks Jan 23, 2024
@jotaen jotaen changed the title Define (and implement) behaviour for hardlinks Define and implement behaviour for hardlinks Jan 23, 2024
@jotaen
Copy link
Owner Author

jotaen commented Jan 23, 2024

Splitting symlinks into its own issue, as it’s actually a separate topic.

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

1 participant