From 4b4795ec8500695465b6691ecdc2e4e38dedbdf7 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Wed, 29 Jun 2022 14:30:57 -0400 Subject: [PATCH] this is fixed --- doc/bugs/Adjust_--unlock_not_using_--reflink__63__.mdwn | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/doc/bugs/Adjust_--unlock_not_using_--reflink__63__.mdwn b/doc/bugs/Adjust_--unlock_not_using_--reflink__63__.mdwn index 91a69a4ea3..ad2187ae8b 100644 --- a/doc/bugs/Adjust_--unlock_not_using_--reflink__63__.mdwn +++ b/doc/bugs/Adjust_--unlock_not_using_--reflink__63__.mdwn @@ -13,3 +13,8 @@ Run adjust --unlock with very large files. ### Have you had any luck using git-annex before? (Sometimes we get tired of reading bug reports all day and a lil' positive end note does wonders) Yes I have! I've used it manage lots of video editing disks before, and am now migrating several slightly different copies of 15TB sized documentary footage from random USB3 disks and LTO tapes to a RAID server with BTRFS. + +> Yay, this got fixed some time ago, by making the smudge filter not output +> the file content at all, but instead the link, and having a git hook +> later run git-annex to populate the files, which it does use reflink for +> when possible. [[done]] --[[Joey]]