Merge branch 'master' of ssh://git-annex.branchable.com
This commit is contained in:
commit
d0fe4d7308
6 changed files with 119 additions and 0 deletions
44
doc/bugs/Missing_automounts_block_every_command.mdwn
Normal file
44
doc/bugs/Missing_automounts_block_every_command.mdwn
Normal file
|
@ -0,0 +1,44 @@
|
|||
### Please describe the problem.
|
||||
When a remote is located on a device (network) that systemd is configured to automount but fails to do so, every git-annex command blocks/waits until the automount times out.
|
||||
|
||||
Commands that have to access such a remote (e.g., `sync`, `move`) are are allowed to block, but commands that only operate on the local repository (e.g., `version`, `add`, `calckey`, `find`) or another one (`sync not-doesnotexist`, `move --to=not-doesnotexist`) should not.
|
||||
|
||||
The Bash completion is also affected and blocks at every tab.
|
||||
|
||||
Probably related: git-annex causes **not missing** idle hard drives (as remotes) to spin up for no reason – even for local commands and completions.
|
||||
|
||||
### What steps will reproduce the problem?
|
||||
Add a non-existing mount point to `/etc/fstab`:
|
||||
|
||||
/dev/sdoesnotexist /mnt/doesnotexist ext4 defaults,noauto,x-systemd.automount,x-systemd.device-timeout=10 0 0
|
||||
|
||||
Add a remote pointing to a path on `/mnt/doesnotexist`:
|
||||
|
||||
$ git remote add doesnotexist /mnt/doesnotexist/path/to/repository
|
||||
|
||||
Use any git-annex command and wait for at least `x-systemd.device-timeout`:
|
||||
|
||||
$ time git-annex version > /dev/null
|
||||
real 0m10.433s
|
||||
user 0m0.171s
|
||||
sys 0m0.028s
|
||||
|
||||
### What version of git-annex are you using? On what operating system?
|
||||
|
||||
git-annex version: 6.20171214-g61b515d71d
|
||||
build flags: Assistant Webapp Pairing Testsuite S3(multipartupload)(storageclasses) WebDAV Inotify DBus DesktopNotify ConcurrentOutput TorrentParser MagicMime Feeds
|
||||
dependency versions: aws-0.18 bloomfilter-2.0.1.0 cryptonite-0.24 DAV-1.3.1 feed-1.0.0.0 ghc-8.2.2 http-client-0.5.7.1 persistent-sqlite-2.6.4 torrent-10000.1.1 uuid-1.3.13 yesod-1.4.5
|
||||
key/value backends: SHA256E SHA256 SHA512E SHA512 SHA224E SHA224 SHA384E SHA384 SHA3_256E SHA3_256 SHA3_512E SHA3_512 SHA3_224E SHA3_224 SHA3_384E SHA3_384 SKEIN256E SKEIN256 SKEIN512E SKEIN512 SHA1E SHA1 MD5E MD5 WORM URL
|
||||
remote types: git gcrypt p2p S3 bup directory rsync web bittorrent webdav tahoe glacier ddar hook external
|
||||
local repository version: 5
|
||||
supported repository versions: 3 5 6
|
||||
upgrade supported from repository versions: 0 1 2 3 4 5
|
||||
operating system: linux x86_64
|
||||
|
||||
### Please provide any additional information below.
|
||||
|
||||
`strace` always includes a call to `stat("/mnt/doesnotexist/path/to/repository")`.
|
||||
|
||||
### 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)
|
||||
|
||||
I’m very happy with git-annex (thanks) and use it frequently enough to notice this behavior.
|
|
@ -0,0 +1,10 @@
|
|||
[[!comment format=mdwn
|
||||
username="emanuele"
|
||||
avatar="http://cdn.libravatar.org/avatar/f51cc5c6c3a0eb28faa6491c3cbcfcce"
|
||||
subject="comment 5"
|
||||
date="2018-01-09T08:46:44Z"
|
||||
content="""
|
||||
I can confirm that the permissions I see are set as you say: .git/annex/misctmp is writable by the group. Still, the error message appears here, using git-annex 6.20171211. I will look more in detail into this one. If something interesting pops out, I'll write here.
|
||||
|
||||
Thanks again for your work.
|
||||
"""]]
|
|
@ -0,0 +1,9 @@
|
|||
[[!comment format=mdwn
|
||||
username="joseph.rawson.works@85a210ab8c0e37a0b2d6bb235738b20e23e8878f"
|
||||
nickname="joseph.rawson.works"
|
||||
avatar="http://cdn.libravatar.org/avatar/6b473d5484b68803e8c47eeff9197397"
|
||||
subject="Download playlist"
|
||||
date="2018-01-06T20:34:31Z"
|
||||
content="""
|
||||
Thanks! I'll try testing the ```importfeed``` now!
|
||||
"""]]
|
|
@ -0,0 +1,12 @@
|
|||
[[!comment format=mdwn
|
||||
username="joseph.rawson.works@85a210ab8c0e37a0b2d6bb235738b20e23e8878f"
|
||||
nickname="joseph.rawson.works"
|
||||
avatar="http://cdn.libravatar.org/avatar/6b473d5484b68803e8c47eeff9197397"
|
||||
subject="testing importfeed"
|
||||
date="2018-01-06T21:57:06Z"
|
||||
content="""
|
||||
I tested importfeed. It seemed to be stuck on ```importfeed checking known urls```. The first playlist I tried had 70+ videos, so I tested a shorter playlist and got the same response. I noticed that on the [[tips/downloading_podcasts]] page, only channels are mentions, but not playlists. However, you mentioned playlists in your response. I was able to work around the issue:
|
||||
|
||||
```for _id in `youtube-dl 'https://www.youtube.com/watch?v=ps40Uminvno&list=PLWnVxuqvY7Jj2Z8aeR-qKXACCXUN4Ouv_' --get-id` ; do echo \"https://www.youtube.com/watch?v=${_id}\" ; done | git-annex addurl --batch --jobs 2```
|
||||
|
||||
"""]]
|
|
@ -0,0 +1,33 @@
|
|||
Hello,
|
||||
|
||||
I have an repo that uses standard groups / wanted expressions:
|
||||
|
||||
% git annex wanted . && git annex group .
|
||||
standard
|
||||
archive backup
|
||||
|
||||
I use the two groups so that the repo wants anything (backup) and is recognized as an archive repo, so other repos drop files in archive/.
|
||||
|
||||
% git annex drop fortune
|
||||
drop fortune (checking S3...) ok
|
||||
(recording state in git...)
|
||||
|
||||
fine. But:
|
||||
|
||||
% git annex get --auto
|
||||
|
||||
does nothing. I do not understand, why the repo does not want the file. Same for git annex sync --content.
|
||||
|
||||
% git annex whereis fortune
|
||||
whereis fortune (3 copies)
|
||||
19317658-7d40-4412-94ba-a2525e625283 -- Asaru
|
||||
2f41eb74-5f33-4737-bb6b-1cd31dd67ee5 -- External
|
||||
728648bf-5276-4a86-9df9-9a30f4783027 -- [S3]
|
||||
ok
|
||||
|
||||
Asaru is standard/client, S3 is standard/backup and External has no group / wanted set.
|
||||
|
||||
|
||||
|
||||
Thanks,
|
||||
Florian
|
|
@ -0,0 +1,11 @@
|
|||
[[!comment format=mdwn
|
||||
username="davicastro"
|
||||
avatar="http://cdn.libravatar.org/avatar/4e708663cf4d5b9e8cfea74caf4307fc"
|
||||
subject="any drawbacks in using --shared (hardlinks) clones on same Linux machine?"
|
||||
date="2018-01-07T00:37:10Z"
|
||||
content="""
|
||||
Hi, I'm new to git and we might be adopting it on next project solely because of git annex!
|
||||
As our files are quite big, having users cloning the repository with --shared is very very nice!
|
||||
We use Linux, so no issue with hardlinks. I did some testing and so far so good. No duplicated space is very very nice!
|
||||
But I'm wondering: is there any disadvantage on this approach?
|
||||
"""]]
|
Loading…
Reference in a new issue