On Sun, Oct 20, 2013 at 11:33:56AM +0100, Phil Davis wrote:
> The reason I think btrfs send is leaking open files is if you watch
> /proc/sys/fs/file-nr you see the
> number of open files increasing but if you kill the btrfs send
> process then the open
> files count reduces back down. In fact suspending the process also
> reduces the open file count but
> resuming it then makes the count start increasing again.
What does lsof show while you are running that? AFAICS, btrfs_ioctl_send()
should be neutral wrt file references - we do fget() on entry and
fput() of the result on exit, with nothing else looking relevant in
sight... OTOH, btrfs-progs number of calls of that ioctl() seems to
be bounded by the length of argument list. So the interesting questions
are
a) how many btrfs send instances are running at the time?
b) what do their arg lists look like?
c) who (if anyone) has all those opened files in their descriptor
tables?
BTW, looking at do_send()...
if (g_verbose > 0)
fprintf(stderr, "joining genl thread\n");
close(pipefd[1]);
pipefd[1] = 0;
ret = pthread_join(t_read, &t_err);
...
if (subvol_fd != -1)
close(subvol_fd);
if (pipefd[0] != -1)
close(pipefd[0]);
if (pipefd[1] != -1)
close(pipefd[1]);
That pipefd[1] = 0; looks bogus; it doesn't look like it could result in
what you are seeing, but unless I'm misreading that code it ought to be
pipefd[1] = -1...
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
