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

Hardlinks #3

Closed
jornodberg opened this issue Apr 11, 2019 · 2 comments · Fixed by #4
Closed

Hardlinks #3

jornodberg opened this issue Apr 11, 2019 · 2 comments · Fixed by #4

Comments

@jornodberg
Copy link

Hi.

Thanks for fastar! We have a backupserver, and loads of small files, and after upgrading the hardware, I got really disappointed by 'tar' when the speed didn't increase as much as I was expecting.
It hit me that we didn't utilize the 'queue depth' of the disks when running tar. And then I found fastar, from a post on StackExchange.

But, I now suspect that 'fastar' don't respect hardlinks. I'm just running a test, and so far I see that the test have copied a lot more data than the original data I'm copying. And our data consists of insane amount of hardlinks (don't ask why.... ;) ... We're doing a kind of virtualization, and utilizing hardlinks of all files which are the same across virtual machines).

Would it be possible to get 'fastar' to understand hardlinks and keep them? Or would that not be possible with the way 'fastar' is made?

@the8472
Copy link
Owner

the8472 commented Apr 11, 2019

Probably possible, I'll have to look how hardlinks are encoded and whether the tar crate supports it.

@the8472
Copy link
Owner

the8472 commented Apr 19, 2019

The tar-rs dependency currently doesn't support the necessary API to add hardlinks. See alexcrichton/tar-rs#119 and alexcrichton/tar-rs#192

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

Successfully merging a pull request may close this issue.

2 participants