You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I tried this tutorial to reproduce and got some error.
During the tutorial, dvc add command should not copy cashed data. But as you can see below the total folder size is doubled.
aiml/tutorial_dvc/classify master
▶ du -sh data
41M data
aiml/tutorial_dvc/classify master
▶ du -sh .dvc/cache
41M .dvc/cache
aiml/tutorial_dvc/classify master
▶ du -sh .
82M .
Reflinks to nodes are different. Maybe it's the case. Let me know if you need some extra information about my environment.
aiml/tutorial_dvc/classify master
▶ ls -i data/Posts.xml.zip
4690717 data/Posts.xml.zip
aiml/tutorial_dvc/classify master
▶ ls -i .dvc/cache/ec/
4688793 1d2935f811b77cc49b031b999cbf17
The text was updated successfully, but these errors were encountered:
Your system supports reflinks, so dvc used them to create a link from cache to your workspace. No data duplication has occurred. Unlike hardlink, reflink to a file has different inode, so it is a bit harder to see it working for yourself. Also, du utility still counts them as two separate full-blown files, even though there is no duplication on the filesystem level. We should definitely make it more clear in the documentation. Created iterative/dvc.org#139 .
Also, to be sure that no duplication occurs, you could take a look at the free space on your drive using df utility, which will show that your free space didn't go down once again by that file size after you've dvc add-ed it.
Information about the environment
Installed with macOS package to macOS Mojave.
Bug report
I tried this tutorial to reproduce and got some error.
During the tutorial,
dvc add
command should not copy cashed data. But as you can see below the total folder size is doubled.Reflinks to nodes are different. Maybe it's the case. Let me know if you need some extra information about my environment.
The text was updated successfully, but these errors were encountered: