From 0e7054e5e55ecf6ac1df517f8fb684a76534ea6d Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Tue, 9 Jan 2018 16:44:10 -0400 Subject: comment --- ...ent_3_c7d5015db5aea0dd4d2ed67803ee9c92._comment | 25 ++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 doc/bugs/Missing_automounts_block_every_command/comment_3_c7d5015db5aea0dd4d2ed67803ee9c92._comment diff --git a/doc/bugs/Missing_automounts_block_every_command/comment_3_c7d5015db5aea0dd4d2ed67803ee9c92._comment b/doc/bugs/Missing_automounts_block_every_command/comment_3_c7d5015db5aea0dd4d2ed67803ee9c92._comment new file mode 100644 index 000000000..a2dae9620 --- /dev/null +++ b/doc/bugs/Missing_automounts_block_every_command/comment_3_c7d5015db5aea0dd4d2ed67803ee9c92._comment @@ -0,0 +1,25 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2018-01-09T20:29:40Z" + content=""" +There would still be some cases where a git-annex command blocks somewhat +unexpectedly on the automount. + +For one, `git annex drop` can need to +check if content is in a remote, and so would block, despite not acting +directly on that remote. + +And, `git annex get` of a file that's located in +such an locally automounted remote and a network remote will +default to trying the local remote first, and so would block. + +The cost of the automounted remote could be adjusted to make these commands +prefer some other remote, but then you've configured git-annex to not +use the automounted remote much, which is probably not what you really want +to do if it's a fast drive. + +Of course, there are also ways to automount removable drives when they get +plugged in, rather than using automounts that block on access, and so +neatly avoid all blocking problems. +"""]] -- cgit v1.2.3