[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: 2.5.59 ext3 error message

On Mar 02, 2003  13:56 +0200, Madis Janson wrote:
> VFS: brelse: Trying to free free buffer
> buffer layer error at fs/buffer.c:1182
> Pass this trace through ksymoops for reporting
> Call Trace: [<c01468f0>]  [<c0146aa9>]  [<c0146b57>]  [<c0146b84>]  [<c0175a17>]  [<c023cbfa>]  [<c023d2f1>]  [<c0175c90>]  [<c01728e9>]  [<c01ad7d6>]  [<c014d215>]  [<c0154c68>]  [<c0154f79>]  [<c0155126>]  [<c0154f79>]  [<c01540c2>]  [<c0154244>]  [<c0109227>]
> Trace; c01468f0 <__brelse+35/37>
> Trace; c0146aa9 <bh_lru_install+b1/ed>
> Trace; c0146b57 <__find_get_block+72/74>
> Trace; c0146b84 <__getblk+2b/51>
> Trace; c0175a17 <ext3_getblk+ab/2f1>
> Trace; c023cbfa <serio_interrupt+4e/50>
> Trace; c023d2f1 <i8042_interrupt+f5/1ff>
> Trace; c0175c90 <ext3_bread+33/a2>
> Trace; c01728e9 <ext3_readdir+e6/4e0>
> Trace; c01ad7d6 <__copy_to_user_ll+74/78>

Can you verify that you are using htree/indexed directories on this system?
Do this by looking for "dir_index" in the "Filesystem features" line from
"dumpe2fs -h <your disks>".  This is likely the case.

Now, try the patch below, and let us know if you see the problem again.
You should probably do a full fsck for your devices to ensure that there
is no corruption at this time, by doing "touch /forcefsck" and shutting
down and restarting your system.

===== namei.c 1.15 vs edited =====
--- 1.15/fs/ext3/namei.c	Wed Oct  2 01:24:11 2002
+++ edited/namei.c	Sun Mar  2 00:05:03 2003
@@ -530,7 +530,7 @@
 	struct dx_hash_info hinfo;
 	struct buffer_head *bh;
 	struct ext3_dir_entry_2 *de, *top;
-	static struct dx_frame frames[2], *frame;
+	struct dx_frame frames[2], *frame;
 	struct inode *dir;
 	int block, err;
 	int count = 0;

Cheers, Andreas
Andreas Dilger

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]