mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Added a comment

Browse source
This commit is contained in:
http://joeyh.name/ 2013-08-24 19:10:21 +00:00 • committed by admin
parent 45c72cf9c3
commit 869365aad4
1 changed files with 15 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

15
doc/bugs/Resource_exhausted/comment_9_419e24e0b91f569294ece28c42daa246._comment Normal file
View file

@ -0,0 +1,15 @@
[[!comment format=mdwn
username="http://joeyh.name/"
ip="4.154.0.63"
subject="comment 9"
date="2013-08-24T19:10:21Z"
content="""
@Michael how large a copy are you doing? And what kind of remote are you copying the files to?
It would be helpful if you could be more specific about something I could do to reproduce the problem. Without a test case, I am unlikely to fix the bug. With a test case, I'd be surprised if it took long to fix it.
If you have a process running that is experiencing the problem, you can also narrow it down a *lot* by looking at what these leaking pipe file descriptors are pipes to. For example, if you have:
lr-x------ 1 michael michael 64 Aug 10 20:14 895 -> pipe:[2251602]
You can run `find /proc/ -ls 2251602` and find the process at other end of the pipe, and look its pid up in ps to see what command it is.
"""]]