From: Mathieu Chouquet-Stringer <mathieu@csetco.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs bug with g38867a2 and a question
Date: Wed, 21 Sep 2011 20:53:50 +0200 [thread overview]
Message-ID: <20110921185350.GA6618@kashmir> (raw)
Hello all,
I've been using BTRFS for quite some time on this laptop and I just
recompiled the latest kernel from git (3.1.0-rc6-00247-g38867a2). After
a couple minutes, I hit this bug twice (this a hand written transcript,
pics here [1]) kernel BUG at fs/btrfs/inode.c:785!
stack being:
_raw_spin_unlock_irqrestore
__wake_up
btrfs_tree_read_unlock_blocking
free_extent_buffer
run_delalloc_nocow
run_dellaloc_range
free_extent_state
find_lock_delalloc_range.constrpop
__extent_writepage
...
Note the stack trace is exactly the same in these two crashes. Since
google found nothing, I'm asking for your help!
Looking at the source, line 785 is function cow_file_range, code:
BUG_ON(btrfs_is_free_space_inode(root, inode));
My fs (a simple partition on a OCZ-VERTEX2 ssd) is mounted with the
following options:
ssd,discard,autodefrag
with disk space caching as it had been added earlier:
btrfs: disk space caching is enabled
Btrfs detected SSD devices, enabling SSD mode
Anything I could do to help debug this one?
Moreover, I've been experiencing long lags when my computer seems to be
just busy doing writes (right now I'm on 3.1.0-rc6-00067-gf1fcd9f): it's
not hung or anything except all IOs are blocked (hence I can start
anything to see what's going on but I have a gauge on my xfce panel that
goes 100% with writes). After some point, it just recovers and
everything is back to normal. I've tried capturing something with
sysrq-t but I haven't been able to find anything striking. Should I
just submit something similar to this mailing list?
[1] http://mathieu.csetco.com/btrfs-crash1.jpg
http://mathieu.csetco.com/btrfs-crash2.jpg
--
Mathieu Chouquet-Stringer mathieu@csetco.com
The sun itself sees not till heaven clears.
-- William Shakespeare --
next reply other threads:[~2011-09-21 18:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-21 18:53 Mathieu Chouquet-Stringer [this message]
2011-09-21 20:18 ` Btrfs bug with g38867a2 and a question Josef Bacik
2011-09-21 20:35 ` Mathieu Chouquet-Stringer
2011-09-21 23:10 ` David Sterba
2011-09-22 10:13 ` Mathieu Chouquet-Stringer
2011-09-22 11:05 ` David Sterba
2011-09-22 11:35 ` Mathieu Chouquet-Stringer
[not found] ` <CALiWzOg8CQJF7OfMex1uJTa+doDZ8oufV1nAbos99Z4ev-+xKg@mail.gmail.com>
2011-09-22 14:12 ` Josef Bacik
2011-09-22 15:16 ` Mathieu Chouquet-Stringer
2011-09-22 18:22 ` Mathieu Chouquet-Stringer
2011-09-22 19:00 ` Josef Bacik
2011-09-22 19:30 ` Mathieu Chouquet-Stringer
2011-09-22 20:32 ` Mathieu Chouquet-Stringer
2011-09-23 12:55 ` Mathieu Chouquet-Stringer
2011-09-23 14:49 ` Josef Bacik
2011-09-23 15:31 ` Mathieu Chouquet-Stringer
2011-09-23 15:34 ` Josef Bacik
2011-09-23 17:16 ` Mathieu Chouquet-Stringer
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=20110921185350.GA6618@kashmir \
--to=mathieu@csetco.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 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).