From e347c492f92c63d518d5e9341481c4d6a8c1458b Mon Sep 17 00:00:00 2001 From: Jorge Orpinel Date: Thu, 22 Aug 2019 13:07:53 -0700 Subject: [PATCH] tutorial: add note about copy being the default fallback when no reflinks supported per #579 --- static/docs/tutorial/define-ml-pipeline.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/static/docs/tutorial/define-ml-pipeline.md b/static/docs/tutorial/define-ml-pipeline.md index 326d0d3365a..aceee7e1b84 100644 --- a/static/docs/tutorial/define-ml-pipeline.md +++ b/static/docs/tutorial/define-ml-pipeline.md @@ -91,9 +91,11 @@ copy) might take a few minutes. DVC was designed with large data files in mind. This means gigabytes or even hundreds of gigabytes in file size. Instead of copying files from cache to -workspace, DVC can create reflinks or other file link types. (See -[File link types](/docs/user-guide/large-dataset-optimization#file-link-types-for-the-dvc-cache) -.) +workspace, DVC can create reflinks or other file link types. + +> When reflinks are not supported, DVC defaults to copying files to avoid +> problems with other file link types, but these can be enabled easily. See +> [File link types](/docs/user-guide/large-dataset-optimization#file-link-types-for-the-dvc-cache Creating file links is a quick file system operation. So, with DVC you can easily checkout a few dozen files of any size. A file link prevents you from