From: Duncan <1i5t5.duncan@cox.net>
To: 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: Tue, 29 Apr 2014 06:28:39 +0000 (UTC) [thread overview]
Message-ID: <pan$c3e1d$1f669ca6$e80dc3d5$584048c@cox.net> (raw)
In-Reply-To: loom.20140428T222711-911@post.gmane.org
Jaap Pieroen posted on Mon, 28 Apr 2014 20:30:55 +0000 as excerpted:
>> For further reference, whenever you post btrfs fi show, please post
>> btrfs fi df as well, as the two provide complementary information, and
>> the picture without both of them is incomplete.
>>
>> If you'd supplied the btrfs fi df output, we could see what raid level
>> you're running for data/metadata/system, as well as which type of
>> chunks were still left on /dev/sdb.
>
> Yep, I dropped the ball here. I did look in the wiki for a list of
> output required when asking for support, but I couldn't find any. I'll
> make sure I add it to the wiki for the next person.
Thanks. That's likely to be quite practically useful to many people over
time, including me. =:^)
(FWIW, while I mentally appreciate that wikis are there to be user-
edited, in practice I seem to treat them like I do most of the web, read-
only, and never actually seem to get around to changing them at all.
OTOH, I've always enjoyed the give and take of newsgroups and mailing
lists and in practice spend quite a bit of time replying to posts,
hopefully helping others there, which I know I do based on the thanks I
get. So I really /can/ thank you for putting that on the wiki, since
while it's likely to make my job replying to posts easier, in practice
it's something I'd be extremely unlikely to change on the wiki myself,
even on wikis like the btrfs wiki which I highly value and have spent
quite some time reading and much more replying on the related list,
because for whatever reason I personally just seem to have an easier time
replying on-list than I do editing wikis. But I'm sure glad others get
around to editing them. =:^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2014-04-29 6:28 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
2014-04-28 20:30 ` Jaap Pieroen
2014-04-29 6:28 ` Duncan [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='pan$c3e1d$1f669ca6$e80dc3d5$584048c@cox.net' \
--to=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 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).