From: Chris Murphy <lists@colorremedies.com>
To: "Jogi Hofmüller" <jogi@mur.at>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: strange i/o errors with btrfs on raid/lvm
Date: Thu, 24 Sep 2015 11:41:21 -0600 [thread overview]
Message-ID: <CAJCQCtQ3aSfHE3o4nyaKOJjDbxiw87GHW6_JdBC1vnDgQXgGKA@mail.gmail.com> (raw)
In-Reply-To: <560409E7.5020500@mur.at>
On Thu, Sep 24, 2015 at 8:34 AM, Jogi Hofmüller <jogi@mur.at> wrote:
> All this runs on a virtual machine that uses kernel 4.1.3 (Debian build)
> and btrfs-progs v4.0.
Unrelated to the problem but I'd upgrade progs, in case it's ever
needed. 4.1 and 4.2 have tons of bug fixes over 4.0 already.
>
> So finally I would ask what we can do to solve this problem? I also
> appreciate comments to the situation and of course hints to what is
> going on. This is over my head.
The problem description is incomplete without a dmesg. If this is a systemd
system, then I suggest
journalctl -b -l -o short-monotonic > journal.txt
Otherwise you can put in a trimmed /var/log/messages for the current boot.
I think it's best to have kernel messages for the entire boot because the
cause could be buried well before the Btrfs error messages.
Attach that to the mailing list. If it's too big, the best option is file a
bug, attach the file to the bug, and then post the URL for the bug in this
thread. The fallback is put it up somewhere else, the problem there is it
ends up being temporarily available so if someone runs into this thread in
a year your attachment is MIA.
--
Chris Murphy
next prev parent reply other threads:[~2015-09-24 17:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 14:34 strange i/o errors with btrfs on raid/lvm Jogi Hofmüller
2015-09-24 17:41 ` Chris Murphy [this message]
2015-09-25 17:17 ` Chris Murphy
[not found] ` <5605ADE4.5090800@mur.at>
2015-09-25 20:47 ` Chris Murphy
2015-09-28 8:39 ` Jogi Hofmüller
2015-10-02 3:54 ` Russell Coker
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=CAJCQCtQ3aSfHE3o4nyaKOJjDbxiw87GHW6_JdBC1vnDgQXgGKA@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=jogi@mur.at \
--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).