xfs
[Top] [All Lists]

XFS assertion failed: tp->t_blk_res_used <= tp->t_blk_res, file: xfs_tra

To: linux-xfs@xxxxxxxxxxx
Subject: XFS assertion failed: tp->t_blk_res_used <= tp->t_blk_res, file: xfs_trans.c, line: 335
From: KELEMEN Peter <fuji@xxxxxxx>
Date: Sat, 7 Apr 2001 21:46:10 +0200
Organization: ELTE Eotvos Lorand University of Sciences, Budapest, Hungary
Reply-to: KELEMEN Peter <fuji@xxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
Hello,

After a couple of assertion failure-free months, here's a
reproducible one.  I can trigger this by compiling the kernel tree
on a 500M XFS partition, on a Celeron 300 MHz 128M IDE machine.
Attempting to unmount the filesystem after the assertion has been
triggered hangs the umount process:
sys_oldumount->sys_umount->do_umount->shrink_dcache_sb->iput
->linvfs_put_inode->vn_put->xfs_inactive->xfs_inactive_free_eofblocks
->xfs_ilock->xfs_ilock_ra->mraccessf->lock_wait *hang*

xfs_repair 1.2.1 reveals (-n) many errors.  I have the damaged
filesystem handy for poking around with xfs_db.

Kernel is 2.4.3-XFS 2001/04/04 15:42 CEST.

Peter

-- 
    .+'''+.         .+'''+.         .+'''+.         .+'''+.         .+''
 Kelemen Péter     /       \       /       \       /      fuji@xxxxxxx
.+'         `+...+'         `+...+'         `+...+'         `+...+'

Attachment: xfs_trans.assert.backtrace
Description: Text document

Attachment: xfs_trans.assert.xfs_repair.output
Description: Text document

<Prev in Thread] Current Thread [Next in Thread>