From: Roman Kononov <kononov@ftml.net>
To: linux-xfs@oss.sgi.com
Cc: Roman Kononov <kononov@ftml.net>
Subject: Re: failed assertion related to realtime section
Date: Wed, 05 Aug 2009 18:21:37 -0500 [thread overview]
Message-ID: <4A7A1401.7030100@ftml.net> (raw)
In-Reply-To: <bzyiqh21oab.fsf@fransum.emea.sgi.com>
Olaf Weber wrote:
> Roman Kononov writes:
>
>> On 2009-07-16 05:02, Olaf Weber wrote:
>>> A quick test on an available system
>>> running a (much) older kernel runs to completion, so this appears to
>>> be a regression.
>
>> With which kernel version did you run the test?
>
> Heavily-patched 2.6.16, which is what I had readily available at that
> point. But most or all of those patches + additional changes should
> be in current XFS.
>
>>> Figuring out exactly when/where this regressed will take time.
>
>> I went back to 2.6.23 and the same assfail happened with somewhat
>> different call trace:
>
>> Assertion failed: xfs_trans_get_block_res(tp) > 0, file:
>> /home/rk/linux-2.6.23/fs/xfs/xfs_bmap.c, line: 5523
>
>> Call Trace:
>> [<ffffffff80356a08>] xfs_bunmapi+0x8e8/0x1060
>> [<ffffffff80227d2a>] dequeue_entity+0x7a/0xb0
>> [<ffffffff80380608>] xfs_itruncate_finish+0x398/0x5c0
>> [<ffffffff803a2323>] xfs_free_eofblocks+0x263/0x2b0
>> [<ffffffff803a4838>] xfs_release+0x118/0x1e0
>> [<ffffffff803ae42a>] xfs_file_release+0x1a/0x30
>> [<ffffffff802827cd>] __fput+0xcd/0x1e0
>> [<ffffffff8027f5c4>] filp_close+0x54/0x90
>> [<ffffffff80280e3d>] sys_close+0x9d/0x110
>> [<ffffffff8020bc9e>] system_call+0x7e/0x83
>
>> I tried to go back to 2.6.22.19 and older, and the test did not run at
>> all failing to mount:
>
>> XFS: bad version
>> XFS: SB validate failed
>
>> Any suggestions?
>
> For that I had the advantage of being able to just build a fresh XFS
> filesystem for the purpose. If that is what you're doing as well,
> look at disabling the lazy-counters option at mkfs time.
>
I removed lazy-counters as you suggested, and under 2.6.22.19 it mounts
successfully. But still crushes in the same place:
Assertion failed: ((tp)->t_blk_res) > 0, file:
/home/rk/xbase/linux/linux-2.6.22.19/fs/xfs/xfs_bmap.c, line: 5515
Call Trace:
[<ffffffff8034ef86>] xfs_bunmapi+0x8e6/0x1050
[<ffffffff80208042>] __switch_to+0x42/0x310
[<ffffffff80377dc8>] xfs_itruncate_finish+0x398/0x5c0
[<ffffffff803989c1>] xfs_inactive_free_eofblocks+0x221/0x260
[<ffffffff802782c7>] cache_free_debugcheck+0xc7/0x1d0
[<ffffffff8039aee7>] xfs_release+0xc7/0x110
[<ffffffff803a497a>] xfs_file_release+0x1a/0x30
[<ffffffff8027f02d>] __fput+0xcd/0x1e0
[<ffffffff8027bf54>] filp_close+0x54/0x90
[<ffffffff8027d68d>] sys_close+0x9d/0x110
[<ffffffff80209c0e>] system_call+0x7e/0x83
I will try older versions.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-08-05 23:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 22:42 failed assertion related to realtime section Roman Kononov
2009-07-15 12:23 ` Olaf Weber
2009-07-16 0:15 ` Roman Kononov
[not found] ` <bzyfxcxgd3z.fsf@fransum.emea.sgi.com>
2009-08-04 21:04 ` Roman Kononov
[not found] ` <bzyiqh21oab.fsf@fransum.emea.sgi.com>
2009-08-05 23:21 ` Roman Kononov [this message]
2009-08-06 0:38 ` Roman Kononov
2009-08-05 3:58 ` Eric Sandeen
2009-08-05 23:07 ` Roman Kononov
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=4A7A1401.7030100@ftml.net \
--to=kononov@ftml.net \
--cc=linux-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