From: Calvin Walton <calvin.walton@kepstin.ca>
To: Chester <somethingsome2000@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: dmesg filled with btrfs messages
Date: Fri, 18 Oct 2013 15:58:26 -0400 [thread overview]
Message-ID: <1382126306.29286.129.camel@hp-a6734f> (raw)
In-Reply-To: <CAAE6i0ibfsMT5ynHMVm_uxNze6bapeL4kmhVba5Tf-em2_V2nQ@mail.gmail.com>
On Thu, 2013-10-17 at 15:54 -0500, Chester wrote:
> ---------- Forwarded message ----------
> From: Chester <somethingsome2000@gmail.com>
> Date: Thu, Oct 17, 2013 at 3:51 PM
> Subject: dmesg filled with btrfs messages
> To: linux-btrfs <linux-btrfs@vger.kernel.org>
>
>
> It's what looks like the same message repeated over and over again.
> Here's my dmesg: Pasted below is an excerpt. The full netconsole log
> is on pastebin http://pastebin.com/4dQGCL9U
> [ 0.000000] Linux version 3.11.0 (root@NaviLaptop) (gcc version
> 4.6.4 (Funtoo 4.6.4-r2) ) #1 SMP Thu Oct 17 08:33:08 CDT 2013
Unfortunately, the 3.11.0 kernel shipped with some outstanding bugs in
btrfs; the fixes were merged into the 3.12-rc kernels and the stable
kernel 3.11.5 or later.
Please upgrade your kernel to 3.11.5 or later!
--
Calvin Walton <calvin.walton@kepstin.ca>
prev parent reply other threads:[~2013-10-18 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 20:54 dmesg filled with btrfs messages Chester
2013-10-18 19:58 ` Calvin Walton [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=1382126306.29286.129.camel@hp-a6734f \
--to=calvin.walton@kepstin.ca \
--cc=linux-btrfs@vger.kernel.org \
--cc=somethingsome2000@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).