From: K L <intervalmg@gmail.com>
To: xen-devel@lists.xensource.com
Subject: tapdisk2 makes HP multi-core hang
Date: Sat, 29 Jan 2011 22:06:49 -0500 [thread overview]
Message-ID: <AANLkTinY7QV0woO58e2pHArWxvPTpVUBRiKA_rTCSqNx@mail.gmail.com> (raw)
Hi all,
I am running tapdisk2 on HP proliant DL360 and found the following
error when tapdisk2 running for a while. Could any body help me look
at this?
Many thanks,
Jeff
///////////////////////////////////////////////
EXT3-fs error (device tapdeva): ext3_add_entry: bad entry in directory
#2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0,
name_len=0
Aborting journal on device tapdeva.
EXT3-fs error (device tapdeva) in ext3_reserve_inode_write: Journal has aborted
ext3_abort called.
EXT3-fs error (device tapdeva): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
EXT3-fs error (device tapdeva) in start_transaction: Journal has aborted
__journal_remove_journal_head: freeing b_committed_data
BUG: soft lockup detected on CPU#2!
Call Trace:
<IRQ> [<ffffffff8022ef40>] wake_up_process+0x10/0x20
[<ffffffff8025fbed>] softlockup_tick+0xfd/0x130
[<ffffffff80242623>] run_local_timers+0x13/0x20
[<ffffffff8020f53d>] timer_interrupt+0x49d/0x500
[<ffffffff8024aa90>] delayed_work_timer_fn+0x0/0x40
[<ffffffff8026013c>] handle_IRQ_event+0x5c/0xb0
[<ffffffff8026024f>] __do_IRQ+0xbf/0x140
[<ffffffff8020c802>] do_IRQ+0x52/0x70
[<ffffffff8043f626>] evtchn_do_upcall+0x126/0x350
[<ffffffff8020a332>] do_hypervisor_callback+0x1e/0x2c
<EOI> [<ffffffff8030da26>] ext3fs_dirhash+0x206/0x220
[<ffffffff8030a300>] htree_dirblock_to_tree+0x70/0x100
[<ffffffff8030a400>] ext3_htree_fill_tree+0x70/0x220
[<ffffffff802743ce>] __handle_mm_fault+0xb2e/0x12e0
[<ffffffff8030026e>] ext3_readdir+0x1ce/0x5e0
[<ffffffff8028e368>] file_move+0x28/0x60
[<ffffffff802a2930>] filldir+0x0/0xe0
[<ffffffff80252799>] up_read+0x9/0x10
[<ffffffff8021e23f>] do_page_fault+0xcef/0x11c0
[<ffffffff802a2930>] filldir+0x0/0xe0
[<ffffffff802a2b40>] vfs_readdir+0x70/0xc0
[<ffffffff802a2ce3>] sys_getdents+0x83/0xd0
[<ffffffff8020a287>] error_exit+0x0/0x71
[<ffffffff80209b48>] system_call+0x68/0x6d
[<ffffffff80209ae0>] system_call+0x0/0x6d
next reply other threads:[~2011-01-30 3:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-30 3:06 K L [this message]
[not found] ` <1296377821.16034.709.camel@ramone.fritz.box>
[not found] ` <AANLkTinweGBN8bKHM-YHqPPQ+H1KQz5FYvf1gj0NSvjK@mail.gmail.com>
[not found] ` <1296417479.16034.754.camel@ramone.fritz.box>
[not found] ` <AANLkTin+ppg3G1kKPtSS0UurSv1zbfY54C8+6ARYa9kr@mail.gmail.com>
2011-01-31 0:48 ` tapdisk2 makes HP multi-core hang Daniel Stodden
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=AANLkTinY7QV0woO58e2pHArWxvPTpVUBRiKA_rTCSqNx@mail.gmail.com \
--to=intervalmg@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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).