Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Robert Buhren <robert@robertbuhren.de>
To: linux-btrfs@vger.kernel.org
Subject: "btrfs send" fails with having too many open fd's
Date: Sun, 07 Apr 2013 10:58:41 +0200	[thread overview]
Message-ID: <51613541.3080009@robertbuhren.de> (raw)

Hi there,

i'm trying to send/receive a snapshot of my home dir for some time now, 
but in the end it always fails because the maximum number of open fd's 
is exceeded.

Kern log says:

"6,7226,15012711248,-;VFS: file-max limit 799969 reached"


My setup is as follows:

Kernel: 3.9-rc5
btrfs-progs: compiled from git commit: commit 
7854c8b667654502f69e05584729146a06827bc6

btrfs fi show:

Label: none  uuid: ccedbef9-417b-454c-b1d4-8b4220111e6a
     Total devices 1 FS bytes used 177.79GB
     devid    1 size 210.85GB used 210.85GB path /dev/dm-0

Label: 'BACKUP'  uuid: 019e75e4-aa2e-495d-9711-28ef7150b1f3
     Total devices 2 FS bytes used 137.35GB
     devid    2 size 298.09GB used 142.01GB path /dev/sdc1
     devid    1 size 298.09GB used 142.03GB path /dev/sdb1


The send fs is on a dm-crypt device and the receive on a btrfs raid1
A scrub for both fs ran fine without errors.I can however send/receive 
my root fs which is much smaller (~17GB).

The error occurs also if i just use "btrfs send" and pipe the output to 
a file.
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.

If further information is needed, i'd be happy to help. I'm also in 
#btrfs on freenode.

Regards,

Robert


PS: Please respond to my email, i'm not subscribed to the list.


             reply	other threads:[~2013-04-07  9:07 UTC|newest]

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

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=51613541.3080009@robertbuhren.de \
    --to=robert@robertbuhren.de \
    --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