From: "James Johnston" <johnstonj.public@codenest.com>
To: "'mitch'" <msfossen@gmail.com>, "'Duncan'" <1i5t5.duncan@cox.net>,
<linux-btrfs@vger.kernel.org>
Subject: RE: Compression causes kernel crashes if there are I/O or checksum errors (was: RE: kernel BUG at fs/btrfs/volumes.c:5519 when hot-removing device in RAID-1)
Date: Fri, 1 Apr 2016 20:54:40 -0000 [thread overview]
Message-ID: <008e01d18c58$b6b793f0$2426bbd0$@codenest.com> (raw)
In-Reply-To: <1459536804.8310.8.camel@gmail.com>
> I grabbed this part from the log after the machine crashed again
> following trying to transfer a bunch of files that included ones with
> csum errors, let me know if this looks like the same issue you were
> having:
>
Idk? You hit a soft lockup, mine got a "kernel BUG at..."
Your stack trace diverges from mine after bio_endio.
James
prev parent reply other threads:[~2016-04-01 20:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-28 4:41 Compression causes kernel crashes if there are I/O or checksum errors (was: RE: kernel BUG at fs/btrfs/volumes.c:5519 when hot-removing device in RAID-1) James Johnston
2016-03-28 10:26 ` Duncan
2016-03-28 14:34 ` James Johnston
2016-03-29 2:23 ` Duncan
2016-03-29 19:02 ` Mitch Fossen
2016-04-01 18:53 ` mitch
2016-04-01 20:54 ` James Johnston [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='008e01d18c58$b6b793f0$2426bbd0$@codenest.com' \
--to=johnstonj.public@codenest.com \
--cc=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
--cc=msfossen@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).