From: Hugo Mills <hugo@carfax.org.uk>
To: Duncan <1i5t5.duncan@cox.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: "kernel BUG at /home/apw/COD/linux/fs/btrfs/extent_io.c:2116!" when deleting device or balancing filesystem.
Date: Mon, 28 Apr 2014 09:07:50 +0100 [thread overview]
Message-ID: <20140428080750.GA10151@carfax.org.uk> (raw)
In-Reply-To: <pan$2abc$efe882ea$fdd493d$5779ebd8@cox.net>
[-- Attachment #1: Type: text/plain, Size: 961 bytes --]
On Mon, Apr 28, 2014 at 03:26:45AM +0000, Duncan wrote:
> Jaap Pieroen posted on Sun, 27 Apr 2014 18:30:19 +0200 as excerpted:
>
> > Hello,
> >
> > When I try to delete a device from my btrfs filesystem I always get the
> > following kernel bug error:
>
> > kernel BUG at /home/apw/COD/linux/fs/btrfs/extent_io.c:2116!
> > invalid opcode: 0000 [#3] SMP
> > See attached log file for more details.
>
> That's a reasonably common, generic error, simply indicating the kernel
> got an invalid/zero opcode instead of what it was supposed to get, but
> not really saying why, tho the log does give some more info.
More than that -- the invalid opcode is simply the way that the
BUG() and BUG_ON() macros are implemented.
Hugo.
--
=== Hugo Mills: hugo@... carfax.org.uk | darksatanic.net | lug.org.uk ===
PGP key: 65E74AC0 from wwwkeys.eu.pgp.net or http://www.carfax.org.uk
--- People are too unreliable to be replaced by machines. ---
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2014-04-28 8:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-27 16:30 "kernel BUG at /home/apw/COD/linux/fs/btrfs/extent_io.c:2116!" when deleting device or balancing filesystem Jaap Pieroen
2014-04-28 3:26 ` Duncan
2014-04-28 8:07 ` Hugo Mills [this message]
2014-04-28 20:30 ` Jaap Pieroen
2014-04-29 6:28 ` Duncan
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=20140428080750.GA10151@carfax.org.uk \
--to=hugo@carfax.org.uk \
--cc=1i5t5.duncan@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.