From: "Néstor Uribe-Patarroyo" <nesuribe@bloptica.com>
To: linux-btrfs@vger.kernel.org
Subject: Kernel bug after changing raid levels
Date: Mon, 31 Aug 2015 14:06:33 -0400 [thread overview]
Message-ID: <55E497A9.80404@bloptica.com> (raw)
I've filed bug https://bugzilla.kernel.org/show_bug.cgi?id=103811 on a
recent kernel bug I've encountered using btrfs after changing raid level
online.
Let me know if there's any more info I can provide, I haven't formatted
that file system yet.
reply other threads:[~2015-08-31 18:06 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=55E497A9.80404@bloptica.com \
--to=nesuribe@bloptica.com \
--cc=bloptica.kernel@mailnull.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 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.