| To: | kdasu <kdasu.kdev@xxxxxxxxx> |
|---|---|
| Subject: | Re: Kernel 3.3 XFS: Assertion failed: xfs_trans_get_block_res(tp) > 0 |
| From: | Dave Chinner <david@xxxxxxxxxxxxx> |
| Date: | Thu, 30 May 2013 11:53:55 +1000 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| Delivered-to: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <1369842978624-35000.post@xxxxxxxxxxxxx> |
| References: | <1369842978624-35000.post@xxxxxxxxxxxxx> |
| User-agent: | Mutt/1.5.21 (2010-09-15) |
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@xxxxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH 8/9] xfs: add fsgeom flag for v5 superblock support., Dave Chinner |
|---|---|
| Next by Date: | caulking gun&foam gun/Will from Builders Choice Tools, Will |
| Previous by Thread: | Kernel 3.3 XFS: Assertion failed: xfs_trans_get_block_res(tp) > 0, kdasu |
| Next by Thread: | Crash recovery/zero-byte file question, Josh Endries |
| Indexes: | [Date] [Thread] [Top] [All Lists] |