From: Dave Chinner <david@fromorbit.com>
To: kdasu <kdasu.kdev@gmail.com>
Cc: linux-xfs@oss.sgi.com
Subject: Re: Kernel 3.3 XFS: Assertion failed: xfs_trans_get_block_res(tp) > 0
Date: Thu, 30 May 2013 11:53:55 +1000 [thread overview]
Message-ID: <20130530015355.GJ29466@dastard> (raw)
In-Reply-To: <1369842978624-35000.post@n7.nabble.com>
On Wed, May 29, 2013 at 08:56:18AM -0700, kdasu wrote:
> kernel 3.3. instability with
>
> When writing 3 real-time and 1 regular file on disk simultaneously
> (sync is blocking function). the rcu stall detection kicks in every
> time when 3rd-4th attempt.
Doesn't happen on my test rig running a 3.10-rc3 kernel using
default mkfs/mount parameters for a rt fs on x86-64. more
information about your system is needed.
http://xfs.org/index.php/XFS_FAQ#Q:_What_information_should_I_include_when_reporting_a_problem.3F
> XFS: Assertion failed: xfs_trans_get_block_res(tp) > 0, file: fs/xfs/xfs_bmap.c,
> line: 5203
I don't see that either, but that indicates you are probably using a
non-default realtime extent size configuration. That's something
xfs_info output will tell us.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-05-30 1:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 15:56 Kernel 3.3 XFS: Assertion failed: xfs_trans_get_block_res(tp) > 0 kdasu
2013-05-30 1:53 ` Dave Chinner [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-17 16:17 Kamal Dasu
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=20130530015355.GJ29466@dastard \
--to=david@fromorbit.com \
--cc=kdasu.kdev@gmail.com \
--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