From 6dd6f3ccf297d3757302e19a22e1c45009c8581d Mon Sep 17 00:00:00 2001 From: TroisSinges Date: Mon, 14 Oct 2019 09:25:18 +0000 Subject: [PATCH] --- .../S3_copies__58___unsafe_to_drop_from_another_repo__63__.mdwn | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/forum/S3_copies__58___unsafe_to_drop_from_another_repo__63__.mdwn b/doc/forum/S3_copies__58___unsafe_to_drop_from_another_repo__63__.mdwn index 11ca875974..35c363d8a4 100644 --- a/doc/forum/S3_copies__58___unsafe_to_drop_from_another_repo__63__.mdwn +++ b/doc/forum/S3_copies__58___unsafe_to_drop_from_another_repo__63__.mdwn @@ -2,4 +2,4 @@ Hi! A file is present in my local repository (v7), and in a special encrypted repository using S3. Numcopies is set to 1. Whenever I try to drop the file, git-annex says it's "Unable to lock down 1 copy of file that is required to safely drop it" after having been "checking repository-s3... (unsafe)". -What "unsafe" means? When I fsck the file in repository-s3, everything's fine and the file is present. +What does "unsafe" means? When I fsck the file in repository-s3, everything's fine and the file is present.