From: Chris Murphy <lists@colorremedies.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: WARN: volumes.c:2376 btrfs_init_new_device+0xcd8/0xed0 RIP: btrfs_show_devname+0x4b/0xd0
Date: Sun, 17 Apr 2016 20:01:35 -0600 [thread overview]
Message-ID: <CAJCQCtSENroAomPKwpRe1aHRcgaRERek8VVpdtTN0EoETPQrdQ@mail.gmail.com> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=116601
Call traces attached to the bug.
The short version is that after (accidentally) adding a 256K 2nd
device to an existing Btrfs (seed) volume, there's a warning then an
oops and then the system becomes unstable and needs to be rebooted
soon thereafter.
kernel 4.5.0
--
Chris Murphy
reply other threads:[~2016-04-18 2:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAJCQCtSENroAomPKwpRe1aHRcgaRERek8VVpdtTN0EoETPQrdQ@mail.gmail.com \
--to=lists@colorremedies.com \
--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;
as well as URLs for NNTP newsgroup(s).