Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Robert Buhren <robert@robertbuhren.de>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: "btrfs send" fails with having too many open fd's
Date: Mon, 08 Apr 2013 16:30:17 +0200	[thread overview]
Message-ID: <5162D479.5080509@robertbuhren.de> (raw)
In-Reply-To: <20130408131149.GC18193@twin.jikos.cz>

On 08.04.2013 15:11, David Sterba wrote:
> On Sun, Apr 07, 2013 at 10:58:41AM +0200, Robert Buhren wrote:
>> "6,7226,15012711248,-;VFS: file-max limit 799969 reached"
>> Label: 'BACKUP'  uuid: 019e75e4-aa2e-495d-9711-28ef7150b1f3
>>      Total devices 2 FS bytes used 137.35GB
>> It takes a very long time before my system crashes (several hours) so i
>> wasn't able to monitor when exactly the fd's increase.
>> In the beginning "btrfs send" just opens less than 10 fd's, but at some
>> point "btrfs send" must open much more.
> It could be a case of
>
> 1) an endless loop, the file limit you've set is quite high (799969), I
> doubt that so many open fd's are needed at any point.
>
> 2) missing file close after in some error path
>
> The file's are open via
> send_write
>    open_cur_inode_file
>      dentry_open
>
> and closed from callbacks in close_cur_inode_file.
>
> Case 2 looks more realistic, but I don't have an idea what could go
> wrong.
>
> david
Do you have a suggestion on how to debug it further?

Regards,

Robert

      reply	other threads:[~2013-04-08 14:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-07  8:58 "btrfs send" fails with having too many open fd's Robert Buhren
2013-04-08 13:11 ` David Sterba
2013-04-08 14:30   ` Robert Buhren [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5162D479.5080509@robertbuhren.de \
    --to=robert@robertbuhren.de \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox