From: Christoph Anton Mitterer <calestyo@scientia.net>
To: fdmanana@gmail.com, "Stephen R. van den Berg" <srb@cuci.nl>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/send.c:1482
Date: Fri, 01 Jan 2016 01:17:34 +0100 [thread overview]
Message-ID: <1451607454.6313.0.camel@scientia.net> (raw)
In-Reply-To: <CAL3q7H7J_tL89wpZ5DJPX8N-0Dv9-KKpPROOserK+hn8E9O2qA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 255 bytes --]
On Thu, 2015-12-31 at 18:29 +0000, Filipe Manana wrote:
> As for fixing the (very) rare cases where we end up creating empty
> symlinks, it's not trivial to fix.
Would it be reasonable to have btrfs-check list such broken symlinks?
Cheers,
Chris.
[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5313 bytes --]
prev parent reply other threads:[~2016-01-01 0:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-31 16:04 kernel BUG at fs/btrfs/send.c:1482 Stephen R. van den Berg
2015-12-31 16:27 ` Stephen R. van den Berg
2015-12-31 18:29 ` Filipe Manana
2016-01-01 0:17 ` Christoph Anton Mitterer [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=1451607454.6313.0.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=srb@cuci.nl \
/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).