This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] got a bug in a kernel

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] got a bug in a kernel
From: Rudy Setiawan <rudal999@xxxxxxxxx>
Date: Sun, 13 Nov 2005 17:48:27 -0800
Delivery-date: Mon, 14 Nov 2005 01:48:35 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type; b=KkePlqjToIEERalV2o9nh7oF6IO7criCY4iVKvCjtNluXijtF+hz+T2Du6vBIwqYwYD/NGREtnmzMihunkbk1Sca4xsvKsevtAw5zfbFCRuGhPPmXM8CCiw/7Z47H3oZYORM6A0PWJwqkPYPu4Raz6scA5JvuLO4c4TAecmeJcs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
EXT3-fs warning (device loop0): ext3_unlink: Deleting nonexistent file (585548), 0
EXT3-fs warning (device loop0): ext3_unlink: Deleting nonexistent file (585567), 0
sb orphan head is 585567
sb_info orphan list:
  inode loop0:585567 at c2f200dc: mode 100000, nlink 0, next 585548
  inode loop0:585548 at d8908664: mode 100000, nlink 0, next 0
Assertion failure in ext3_put_super() at fs/ext3/super.c:410: "list_empty(&sbi->s_orphan)"
------------[ cut here ]------------
kernel BUG at <bad filename>:10473!
invalid operand: 0000 [#1]
Modules linked in: iptable_filter ip_tables
CPU:    0
EIP:    0061:[<c01be29f>]    Not tainted VLI
EFLAGS: 00011296   (
EIP is at ext3_put_super+0x163/0x181
eax: 0000005e   ebx: df23d828   ecx: 00004af6   edx: 00000000
esi: df23d780   edi: df79fa00   ebp: d004c000   esp: d004df04
ds: 007b   es: 007b   ss: 0069
Process umount (pid: 3996, threadinfo=d004c000 task=dca9aa80)
Stack: c03ecc60 c03d6d5e c03e65bd 0000019a c03e65a2 dfcc040c df79fa00 c043c5e0
       c0159b3c df79fa00 df79fa00 dd3b3700 0805121a c015a621 df79fa00 00000005
       df79fa00 c043c7e0 c0159938 df79fa00 c05177a0 00000000 d004df6c c016f2d3
Call Trace:
 [<c0159b3c>] generic_shutdown_super+0x123/0x139
 [<c015a621>] kill_block_super+0x27/0x44
 [<c0159938>] deactivate_super+0x55/0x78
 [<c016f2d3>] sys_umount+0x39/0x80
 [<c0147ba4>] do_munmap+0x13d/0x191
 [<c0147c36>] sys_munmap+0x3e/0x58
 [<c016f331>] sys_oldumount+0x17/0x1b
 [<c0108d3c>] syscall_call+0x7/0xb
Code: 44 24 10 a2 65 3e c0 c7 44 24 0c 9a 01 00 00 c7 44 24 08 bd 65 3e c0 c7 44 24 04 5e 6d 3d c0 c7 04 24 60 cc 3e c0 e8 a4 bc f5 ff <0f> 0b e9 28 ff ff ff 89 74 24 04 89 3c 24 e8 f7 fd ff ff 8b 86
OS: Fedora Core 3
Kernel: 2.6.11
Hmm maybe this partly was my wrong doing lol.
After creating all the image files including base+devtools.
I forgot to umount the image files and started creating the virtual servers (domU).
Then on the host itself, i did a umount on that partition and the virtual servers started posting alotof ext3-fs errors.
So not sure if this is a kernel bug within the domU kernel or maybe something that i should not have done lol.

Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] got a bug in a kernel, Rudy Setiawan <=