git-annex/doc/bugs/Stress_test/comment_9_9f7efe81b7e40aaa04a865394c53e20f._comment
Joey Hess e213ef310f git-annex (5.20140717) unstable; urgency=high
* Fix minor FD leak in journal code. Closes: #754608
  * direct: Fix handling of case where a work tree subdirectory cannot
    be written to due to permissions.
  * migrate: Avoid re-checksumming when migrating from hashE to hash backend.
  * uninit: Avoid failing final removal in some direct mode repositories
    due to file modes.
  * S3: Deal with AWS ACL configurations that do not allow creating or
    checking the location of a bucket, but only reading and writing content to
    it.
  * resolvemerge: New plumbing command that runs the automatic merge conflict
    resolver.
  * Deal with change in git 2.0 that made indirect mode merge conflict
    resolution leave behind old files.
  * sync: Fix git sync with local git remotes even when they don't have an
    annex.uuid set. (The assistant already did so.)
  * Set gcrypt-publish-participants when setting up a gcrypt repository,
    to avoid unncessary passphrase prompts.
    This is a security/usability tradeoff. To avoid exposing the gpg key
    ids who can decrypt the repository, users can unset
    gcrypt-publish-participants.
  * Install nautilus hooks even when ~/.local/share/nautilus/ does not yet
    exist, since it is not automatically created for Gnome 3 users.
  * Windows: Move .vbs files out of git\bin, to avoid that being in the
    PATH, which caused some weird breakage. (Thanks, divB)
  * Windows: Fix locking issue that prevented the webapp starting
    (since 5.20140707).

# imported from the archive
2014-07-17 11:27:25 -04:00

52 lines
2.2 KiB
Text

[[!comment format=mdwn
username="https://www.google.com/accounts/o8/id?id=AItOawm5iosFbL2By7UFeViqkc6v-hoAtqILeDA"
nickname="Laszlo"
subject="Maybe it is not leaking after all"
date="2013-05-03T18:37:48Z"
content="""
I have been working the whole day zipping up (tar.gz) all the unused directories.
Now my real data dir looks like this:
./annex_real/work_done$ du -hs .
1,1G .
Has 9088 files and 1608 directories in total:
./annex_real/work_done$ ls -R1l |grep \\-r |wc -l
9088
./annex_real/work_done$ ls -R1l |grep ^d |wc -l
1608
When I first started git annex, it added 5492 files, then next time it added the missing 3596 files. Then it stopped adding files.
From the gui everything looked fine even at the first start (performed startup scan), even in the log files (daemon.log.x) was nothing suspicious.
./annex_real/work_done$ for i in ../.git/annex/daemon.log.*; do echo $i; cat $i |grep files; done
../.git/annex/daemon.log.1
../.git/annex/daemon.log.2
../.git/annex/daemon.log.3
../.git/annex/daemon.log.4
[2013-05-03 20:03:34 CEST] Committer: Adding 3596 files
../.git/annex/daemon.log.5
[2013-05-03 19:15:22 CEST] Committer: Adding 5492 files
As you can see, this case is not a stress test at all,
it is really the minimal test case, 1.1GB diskspace, 9088 files and a thousand dirs.
The real question is, why git-annex miss at the first startup 3492 files (ie. adding all the files).
It would help tremendously, if it would display at startup how many files he found,
and when it adds, then how many left to be added.
Something like this:
(scanning...) [2013-05-03 20:03:14 CEST] Watcher: Performing startup scan
(started...)
[2013-05-03 20:03:34 CEST] Committer: Found 9088 files
[2013-05-03 20:03:34 CEST] Committer: Adding 3596 files of 9088 remaining files (9088 in total)
....
[2013-05-03 20:05:04 CEST] Committer: Adding 1492 files of 5492 remaining files (9088 in total)
....
[2013-05-03 20:06:02 CEST] Committer: Adding 4000 files of 4000 remaining files (9088 in total)
So it is definietly a bug, and I stuck how to debug it further. Everything looks just fine.
Best,
Laszlo
"""]]