From: "Szőts Ákos" <szotsaki@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Kernel BUG on corrupted space cache under 3.7 and 3.8
Date: Tue, 26 Mar 2013 12:37:35 +0100 [thread overview]
Message-ID: <1420920.Yent3fKO0t@linux-suse> (raw)
Dear list members,
Yesterday I was about to restart my computer and that's why I closed every
opened applications: three Eclipse instances, two other Java applications, 2
web browsers etc. It involved a lot of IO operations and before everything
could settle down my system became unresponsive.
I mean X & co. worked fine, but anything related to IO (opening a new screen, a
new application etc.) hung. My process explorer showed that nearly all of the
applications which were shutting down have very high IO, but in fact there
were no HDD head movement at all. I did a hard reset.
Today morning when I restarted Linux I got a kernel BUG from btrfs. I
successfully started a recovery Linux (with kernel 3.7) and when I tried to
mount this partition, the bug/panic appeared again. After I could rebuild the
space cache with clear_cache option and my system was fixed.
Since all this logs are written only onto screen, I made some photographs :),
and I uploaded them.
System parameters:
- openSUSE 12.3, Kernel 3.8, x86_64
- Linux linux-suse 3.8.0-5-desktop #1 SMP PREEMPT Tue Feb 26 20:55:05 UTC 2013
(db497a6) x86_64 x86_64 x86_64 GNU/Linux
- Photos are made on Kernel 3.7
- Default mount options: compress=lzo,space_cache
- On 3.7, the problematic line: fs/btrfs/free-space-cache.c:1553
- Photos location: www.morrohun.hu/temp/btrfs/[123].jpeg
If you need any other information, ask me :).
Best regards,
Ákos Szőts
next reply other threads:[~2013-03-26 11:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-26 11:37 Szőts Ákos [this message]
2013-03-26 13:01 ` Kernel BUG on corrupted space cache under 3.7 and 3.8 Josef Bacik
2013-03-26 14:10 ` Szőts Ákos
2013-05-05 18:53 ` Szőts Ákos
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=1420920.Yent3fKO0t@linux-suse \
--to=szotsaki@gmail.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.