From: "Szőts Ákos" <szotsaki@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Kernel BUG at ctree.c:1144 and soft lockup while defragging
Date: Mon, 27 May 2013 21:38:12 +0200 [thread overview]
Message-ID: <2462016.qiZEcvOCVp@linux-suse> (raw)
Dear list,
While I was trying to defrag a specified directory I got kernel BUGs and
warnings about CPUx stucked for twenty-some seconds.
The specified warnings were:
BUG at ctree.c:1144. Invalid opcode: 0000
command: btrfs-endio-wri
Call trace top: btrfs_search_old_slot
The executed command in $HOME/.local:
find -xdev -type f -exec btrfs fi defrag -clzo '{}' \;
After that a soft lockup BUG occurred with systemd-journal with
btrfs_add_delayed_data_ref being on top of the call trace.
Since no log stayed in the journal, I took some pictures and uploaded them
here:
- Ctree bug: www.morrohun.hu/temp/btrfs/IMG_1983.JPG
www.morrohun.hu/temp/btrfs/IMG_1985.JPG
- Soft lockup with systemd-journal: www.morrohun.hu/temp/btrfs/IMG_1995.JPG
- Same stack trace without lockup and with btrfs-endio-wri:
www.morrohun.hu/temp/btrfs/IMG_1996.JPG
System: openSUSE 12.3, kernel 3.9.2-3.g97197ff-desktop.
If you need an image, can I take a snapshot just from the specified directory?
Best regards,
Ákos Szőts
reply other threads:[~2013-05-27 19:38 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=2462016.qiZEcvOCVp@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox