From: Louis-David Mitterrand <vindex+lists-xfs@apartia.org>
To: xfs@oss.sgi.com
Subject: Re: Crash on 2.6.21.7 Vanilla + DRBD 0.7
Date: Wed, 10 Oct 2007 17:15:37 +0200 [thread overview]
Message-ID: <20071010151537.GA31573@apartia.fr> (raw)
In-Reply-To: <4704FA19.2080101@theendofthetunnel.de>
On Thu, Oct 04, 2007 at 04:35:05PM +0200, Hannes Dorbath wrote:
> On 04.10.2007 15:33, vindex+lists-xfs@apartia.org wrote:
>> What do you think about it ?
>
> Another thing, is there a special reason why you use DRBD 0.7.x branch?
> AFAIK it will still deadlock with kernel 2.6.22. You are not running .22,
> but if you upgrade you might have serious problems. You should really go
> with DRBD 8.0.6 if you can.
>
After upgrading to 8.0.6 we had another xfs-related crash 4 days later.
In desperation we are about to abandon xfs and convert this huge
partition to ext3. Is there anyting else we could try before taking that
step?
Thanks,
Oct 9 12:20:05 sargon/sargon kernel: SMP
Oct 9 12:20:05 sargon/sargon kernel: CPU: 1
Oct 9 12:20:05 sargon/sargon kernel: EIP: 0060:[<c015edc2>] Not tainted VLI
Oct 9 12:20:05 sargon/sargon kernel: EFLAGS: 00010082 (2.6.22-dl380-g5-20070917 #1)
Oct 9 12:20:05 sargon/sargon kernel: EIP is at free_block+0x67/0xfe
Oct 9 12:20:05 sargon/sargon kernel: eax: a9b1fb46 ebx: 00000000 ecx: f65f4200 edx: d9741040
Oct 9 12:20:05 sargon/sargon kernel: esi: f65f4000 edi: f79e8f40 ebp: f79da680 esp: f797de5c
Oct 9 12:20:05 sargon/sargon kernel: ds: 007b es: 007b fs: 00d8 gs: 0000 ss: 0068
Oct 9 12:20:05 sargon/sargon kernel: Process kswapd0 (pid: 248, ti=f797c000 task=f7c22a90 task.ti=f797c000)
Oct 9 12:20:05 sargon/sargon kernel: Stack: 00000000 00000000 0000001b 00000010 f79e9f14 0000001b 000000d8 f79da680
Oct 9 12:20:05 sargon/sargon kernel: f79e8f40 c015eb6e 00000000 f79e9ec0 f79e9ec0 00000246 cb353240 00000001
Oct 9 12:20:05 sargon/sargon kernel: c015eca7 cb353240 f52f2cf0 dbe833c0 c0210cd0 00000001 dbe833dc dbe833c0
Oct 9 12:20:05 sargon/sargon kernel: Call Trace:
Oct 9 12:20:05 sargon/sargon kernel: [<c015eb6e>] cache_flusharray+0x70/0x96
Oct 9 12:20:05 sargon/sargon kernel: [<c015eca7>] kmem_cache_free+0x7d/0x96
Oct 9 12:20:05 sargon/sargon kernel: [<c0210cd0>] xfs_finish_reclaim+0x121/0x129
Oct 9 12:20:05 sargon/sargon kernel: [<c021e892>] xfs_fs_clear_inode+0x8f/0xb1
Oct 9 12:20:05 sargon/sargon kernel: [<c0172379>] clear_inode+0xa2/0xf0
Oct 9 12:20:05 sargon/sargon kernel: [<c0172639>] dispose_list+0x46/0xc2
Oct 9 12:20:05 sargon/sargon kernel: [<c0172841>] shrink_icache_memory+0x18c/0x1b4
Oct 9 12:20:05 sargon/sargon kernel: [<c014ca77>] shrink_slab+0xd9/0x138
Oct 9 12:20:05 sargon/sargon kernel: [<c014ce04>] kswapd+0x297/0x3e8
Oct 9 12:20:05 sargon/sargon kernel: [<c012d2f1>] autoremove_wake_function+0x0/0x35
Oct 9 12:20:05 sargon/sargon kernel: [<c014cb6d>] kswapd+0x0/0x3e8
Oct 9 12:20:05 sargon/sargon kernel: [<c012d22b>] kthread+0x38/0x5d
Oct 9 12:20:05 sargon/sargon kernel: [<c012d1f3>] kthread+0x0/0x5d
Oct 9 12:20:05 sargon/sargon kernel: [<c0104963>] kernel_thread_helper+0x7/0x10
Oct 9 12:20:05 sargon/sargon kernel: =======================
Oct 9 12:20:05 sargon/sargon kernel: Code: 00 3d 00 40 02 00 75 03 8b 52 0c 8b 02 84 c0 78 04 0f 0b eb fe 8b 72 1c 8b 54 24 28 8b 46 04 8b bc 95 88 00 00 00 8b 16 89 42 04 <89> 10 2b 4e 0c c7 06 00 01 10 00 c7 46 04 00 02 20 00 89 c8 f7
Oct 9 12:20:05 sargon/sargon kernel: EIP: [<c015edc2>] free_block+0x67/0xfe SS:ESP 0068:f797de5c
next prev parent reply other threads:[~2007-10-10 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-04 13:33 Crash on 2.6.21.7 Vanilla + DRBD 0.7 vindex+lists-xfs
2007-10-04 14:27 ` Hannes Dorbath
2007-10-04 16:42 ` Laurent CARON
2007-10-04 14:35 ` Hannes Dorbath
2007-10-04 16:33 ` Laurent CARON
2007-10-10 15:15 ` Louis-David Mitterrand [this message]
2007-10-10 22:46 ` David Chinner
2007-10-11 7:36 ` Laurent CARON
2007-10-04 23:10 ` David Chinner
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=20071010151537.GA31573@apartia.fr \
--to=vindex+lists-xfs@apartia.org \
--cc=xfs@oss.sgi.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