summaryrefslogtreecommitdiff
path: root/doc/bugs/Resource_exhausted
diff options
context:
space:
mode:
authorGravatar http://joeyh.name/ <http://joeyh.name/@web>2013-08-24 19:10:21 +0000
committerGravatar admin <admin@branchable.com>2013-08-24 19:10:21 +0000
commit3f63264d8ef6a3d9a96cd080b4f56890d324cfbd (patch)
tree57c38a3752c83e86e7d22879e7dfb52d2a2d8ad0 /doc/bugs/Resource_exhausted
parent9cb72d49d3888b274b24855d2ef84d7b4710794a (diff)
Added a comment
Diffstat (limited to 'doc/bugs/Resource_exhausted')
-rw-r--r--doc/bugs/Resource_exhausted/comment_9_419e24e0b91f569294ece28c42daa246._comment15
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/bugs/Resource_exhausted/comment_9_419e24e0b91f569294ece28c42daa246._comment b/doc/bugs/Resource_exhausted/comment_9_419e24e0b91f569294ece28c42daa246._comment
new file mode 100644
index 000000000..0e06f5af9
--- /dev/null
+++ b/doc/bugs/Resource_exhausted/comment_9_419e24e0b91f569294ece28c42daa246._comment
@@ -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.
+"""]]