From: Roman Kononov <kononov@ftml.net>
To: linux-xfs@oss.sgi.com
Subject: Re: failed assertion related to realtime section
Date: Wed, 05 Aug 2009 19:38:18 -0500 [thread overview]
Message-ID: <4A7A25FA.4050201@ftml.net> (raw)
In-Reply-To: <bzyiqh21oab.fsf@fransum.emea.sgi.com>
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.
Did you have the XFS_DEBUG option on? Without it, the filesystem with
realtime does not die right away, but hangs or crashes later.
>
>> 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.
>
Vanilla 2.6.16.19 without the lazy-counters option:
Assertion failed: ((tp)->t_blk_res) > 0, file:
/home/rk/linux-2.6.16.19/fs/xfs/xfs_bmap.c, line: 5452
Call Trace:
<ffffffff801e4b3f>{xfs_bunmapi+1335}
<ffffffff8020c5c0>{xfs_itruncate_finish+769}
<ffffffff8022be3c>{xfs_inactive_free_eofblocks+420}
<ffffffff8022bf40>{xfs_release+190}
<ffffffff80232e27>{linvfs_release+26}
<ffffffff80169c60>{__fput+189}
<ffffffff8016733a>{filp_close+93}
<ffffffff801673db>{sys_close+150}
<ffffffff8010aa2a>{system_call+126}
It looks like it never worked.
Any hope? :-(
Roman
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-08-06 0:37 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
2009-08-06 0:38 ` Roman Kononov [this message]
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=4A7A25FA.4050201@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