From: David Sterba <dsterba@suse.cz>
To: Phil Davis <pmdhazy@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: btrfs send 'leaks' open files
Date: Mon, 21 Oct 2013 15:02:34 +0200 [thread overview]
Message-ID: <20131021130234.GL1032@twin.jikos.cz> (raw)
In-Reply-To: <CAERquQ78pOig3oQoom2e0Jcsv1i3-_8ET0ewAWUUo+nt2vk4Mg@mail.gmail.com>
On Sun, Oct 20, 2013 at 11:33:56AM +0100, Phil Davis wrote:
> I also found Robert Buhren reporting very similar issue back in April 2013:
> http://comments.gmane.org/gmane.comp.file-systems.btrfs/24795
>
> If further information is needed, i'd be happy to help.
Please open bug at bugzilla.kernel.org.
thanks
next prev parent reply other threads:[~2013-10-21 13:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-20 10:33 btrfs send 'leaks' open files Phil Davis
2013-10-21 13:02 ` David Sterba [this message]
2013-10-22 17:22 ` Al Viro
2013-10-22 17:39 ` Al Viro
2013-10-22 20:41 ` Al Viro
2013-10-22 21:07 ` Josef Bacik
2013-10-22 21:22 ` Zach Brown
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=20131021130234.GL1032@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=pmdhazy@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).