Re: Kernel crash in xfs_iflush_cluster (was Somebody take a look please!...)

[Janos Haar]

----- Original Message ----- 
From: "Dave Chinner" <david@xxxxxxxxxxxxx>
To: "Janos Haar" <janos.haar@xxxxxxxxxxxx>
Cc: <xiyou.wangcong@xxxxxxxxx>; <linux-kernel@xxxxxxxxxxxxxxx>; 
<kamezawa.hiroyu@xxxxxxxxxxxxxx>; <linux-mm@xxxxxxxxx>; <xfs@xxxxxxxxxxx>; 
<axboe@xxxxxxxxx>
Sent: Monday, April 12, 2010 2:11 AM
Subject: Re: Kernel crash in xfs_iflush_cluster (was Somebody take a look 
please!...)


> On Mon, Apr 12, 2010 at 12:44:37AM +0200, Janos Haar wrote:
> > Hi,
> >
> > Ok, here comes the funny part:
> > I have got several messages from the kernel about one of my XFS
> > (sdb2) have corrupted inodes, but my xfs_repair (v. 2.8.11) says the
> > FS is clean and shine.
> > Should i upgrade my xfs_repair, or this is another bug? :-)
>
> v2.8.11 is positively ancient. :/
>
> I'd upgrade (current is 3.1.1) and re-run repair again.

OK, i will get the new repair today.

btw
Since i tested the FS with the 2.8.11, today morning i found this in the 
log:

...
Apr 12 00:41:10 alfa kernel: XFS mounting filesystem sdb2   # This was the 
point of check with xfs_repair v2.8.11
Apr 13 03:08:33 alfa kernel: xfs_da_do_buf: bno 32768
Apr 13 03:08:33 alfa kernel: dir: inode 474253931
Apr 13 03:08:33 alfa kernel: Filesystem "sdb2": XFS internal error 
xfs_da_do_buf(1) at line 2020 of file fs/xfs/xfs_da_btree.c.  Caller 
0xffffffff811c4fa6
Apr 13 03:08:33 alfa kernel:
Apr 13 03:08:33 alfa kernel: Pid: 27304, comm: 01vegzet_runner Not tainted 
2.6.32.10 #3
Apr 13 03:08:33 alfa kernel: Call Trace:
Apr 13 03:08:33 alfa kernel:  [<ffffffff811cf87d>] 
xfs_error_report+0x41/0x43
Apr 13 03:08:33 alfa kernel:  [<ffffffff811c4fa6>] ? 
xfs_da_read_buf+0x2a/0x2c
Apr 13 03:08:33 alfa kernel:  [<ffffffff811c4c30>] xfs_da_do_buf+0x2a6/0x5aa
Apr 13 03:08:33 alfa kernel:  [<ffffffff811c4fa6>] xfs_da_read_buf+0x2a/0x2c
Apr 13 03:08:33 alfa kernel:  [<ffffffff811ca0f1>] ? 
xfs_dir2_leaf_lookup_int+0x104/0x259
Apr 13 03:08:33 alfa kernel:  [<ffffffff811ca0f1>] 
xfs_dir2_leaf_lookup_int+0x104/0x259
Apr 13 03:08:33 alfa kernel:  [<ffffffff811ca56e>] 
xfs_dir2_leaf_lookup+0x26/0xb5
Apr 13 03:08:33 alfa kernel:  [<ffffffff811c6d60>] ? 
xfs_dir2_isleaf+0x21/0x52
Apr 13 03:08:33 alfa kernel:  [<ffffffff811c74ea>] 
xfs_dir_lookup+0x104/0x157
Apr 13 03:08:33 alfa kernel:  [<ffffffff811eab59>] xfs_lookup+0x50/0xb3
Apr 13 03:08:33 alfa kernel:  [<ffffffff811f5a8f>] xfs_vn_lookup+0x45/0x86
Apr 13 03:08:33 alfa kernel:  [<ffffffff810e4164>] __lookup_hash+0x105/0x12a
Apr 13 03:08:33 alfa kernel:  [<ffffffff810e41c4>] lookup_hash+0x3b/0x40
Apr 13 03:08:33 alfa kernel:  [<ffffffff810e7021>] do_unlinkat+0x71/0x17d
Apr 13 03:08:33 alfa kernel:  [<ffffffff8175d2d3>] ? 
trace_hardirqs_on_thunk+0x3a/0x3f
Apr 13 03:08:33 alfa kernel:  [<ffffffff810e5a1d>] ? putname+0x3c/0x3e
Apr 13 03:08:33 alfa kernel:  [<ffffffff810e7143>] sys_unlink+0x16/0x18
Apr 13 03:08:33 alfa kernel:  [<ffffffff8100b09b>] 
system_call_fastpath+0x16/0x1b
....

The entire log is here:
http://download.netcenter.hu/bughunt/20100413/messages

What is the best next step?
Check with the new repair?

Thanks,
Janos


> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@xxxxxxxxxxxxx
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/ 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/