* xfs 2.6.31.9 error
@ 2009-12-28 15:10 DS
2009-12-28 23:22 ` Dave Chinner
0 siblings, 1 reply; 3+ messages in thread
From: DS @ 2009-12-28 15:10 UTC (permalink / raw)
To: xfs
Hello,
after upgrade from Debian etch -> Debian lenny with custom kernel 2.6.31.9 (before 2.6.28.1) I see this error and server is resetting sometimes.
Filesystem was creating far far away (about 4years ago).
Dusan
XFS internal error XFS_WANT_CORRUPTED_RETURN at line 366 of file fs/xfs/xfs_alloc.c. Caller 0xffffffff81169ae3
Pid: 4022, comm: procmail Not tainted 2.6.31.9 #3
Call Trace:
[<ffffffff8118edfe>] xfs_error_report+0x3e/0x40
[<ffffffff81169ae3>] ? xfs_alloc_ag_vextent_near+0x3f3/0x940
[<ffffffff811680fa>] xfs_alloc_fixup_trees+0x2ba/0x340
[<ffffffff81167de9>] ? xfs_alloc_get_rec+0x29/0x60
[<ffffffff81169ae3>] xfs_alloc_ag_vextent_near+0x3f3/0x940
[<ffffffff8116a105>] xfs_alloc_ag_vextent+0xd5/0x130
[<ffffffff8116aa68>] xfs_alloc_vextent+0x3a8/0x4f0
[<ffffffff81176ff7>] xfs_bmap_btalloc+0x5b7/0xa30
[<ffffffff81177479>] xfs_bmap_alloc+0x9/0x10
[<ffffffff8117976e>] xfs_bmapi+0x96e/0x10e0
[<ffffffff813aafcc>] ? __down_write_nested+0x1c/0xc0
[<ffffffff8119a5df>] xfs_iomap_write_allocate+0x23f/0x3c0
[<ffffffff8119b1ce>] xfs_iomap+0x2ce/0x300
[<ffffffff811b3817>] xfs_map_blocks+0x27/0x30
[<ffffffff811b498b>] xfs_page_state_convert+0x46b/0x720
[<ffffffff811ef768>] ? __up_write+0xd8/0x140
[<ffffffff811b4f55>] xfs_vm_writepage+0x75/0x120
[<ffffffff8107bf52>] __writepage+0x12/0x50
[<ffffffff8107c877>] write_cache_pages+0x227/0x460
[<ffffffff8107bf40>] ? __writepage+0x0/0x50
[<ffffffff811b7f5d>] ? xfs_file_aio_write+0x5d/0x70
[<ffffffff810a2861>] ? do_sync_write+0xf1/0x140
[<ffffffff8107cacf>] generic_writepages+0x1f/0x30
[<ffffffff811b4ea6>] xfs_vm_writepages+0x56/0x70
[<ffffffff8107cb08>] do_writepages+0x28/0x50
[<ffffffff81076541>] __filemap_fdatawrite_range+0x51/0x60
[<ffffffff810775fa>] filemap_fdatawrite+0x1a/0x20
[<ffffffff810c58b0>] vfs_fsync+0x70/0x100
[<ffffffff810c5979>] do_fsync+0x39/0x60
[<ffffffff810c59cb>] sys_fsync+0xb/0x10
[<ffffffff8100bd6b>] system_call_fastpath+0x16/0x1b
~
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: xfs 2.6.31.9 error
2009-12-28 15:10 xfs 2.6.31.9 error DS
@ 2009-12-28 23:22 ` Dave Chinner
2010-01-06 9:02 ` xfs 2.6.31.9 error - possibly SOLVED DS
0 siblings, 1 reply; 3+ messages in thread
From: Dave Chinner @ 2009-12-28 23:22 UTC (permalink / raw)
To: DS; +Cc: xfs
On Mon, Dec 28, 2009 at 04:10:48PM +0100, DS wrote:
> Hello,
>
> after upgrade from Debian etch -> Debian lenny with custom kernel
> 2.6.31.9 (before 2.6.28.1) I see this error and server is
> resetting sometimes..
>
> Filesystem was creating far far away (about 4years ago).
>
> XFS internal error XFS_WANT_CORRUPTED_RETURN at line 366 of file fs/xfs/xfs_alloc.c. Caller 0xffffffff81169ae3
Any errors in the log before this (e.g. IO errors)?
> Pid: 4022, comm: procmail Not tainted 2.6.31.9 #3
> Call Trace:
> [<ffffffff8118edfe>] xfs_error_report+0x3e/0x40
> [<ffffffff811680fa>] xfs_alloc_fixup_trees+0x2ba/0x340
> [<ffffffff81167de9>] ? xfs_alloc_get_rec+0x29/0x60
> [<ffffffff81169ae3>] xfs_alloc_ag_vextent_near+0x3f3/0x940
> [<ffffffff8116a105>] xfs_alloc_ag_vextent+0xd5/0x130
> [<ffffffff8116aa68>] xfs_alloc_vextent+0x3a8/0x4f0
.....
Looks like a corrupted free space tree - that could have happened a
long time ago and only now are you tripping over it. I'd run
xfs_repair on the filesystem to fix up the problem. If it happens
again then we'll have to look deeper.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: xfs 2.6.31.9 error - possibly SOLVED
2009-12-28 23:22 ` Dave Chinner
@ 2010-01-06 9:02 ` DS
0 siblings, 0 replies; 3+ messages in thread
From: DS @ 2010-01-06 9:02 UTC (permalink / raw)
To: xfs
There was something wrong with the old FS and the kernel 2.6.31.9 (unable to replay log) has not been of much help.
All works fine with kernel 2.6.27.42 and new clear FS for a few days .
Thanks.
Dusan
On Tue, Dec 29, 2009 at 10:22:04AM +1100, Dave Chinner wrote:
> On Mon, Dec 28, 2009 at 04:10:48PM +0100, DS wrote:
> > Hello,
> >
> > after upgrade from Debian etch -> Debian lenny with custom kernel
> > 2.6.31.9 (before 2.6.28.1) I see this error and server is
> > resetting sometimes..
> >
> > Filesystem was creating far far away (about 4years ago).
> >
> > XFS internal error XFS_WANT_CORRUPTED_RETURN at line 366 of file fs/xfs/xfs_alloc.c. Caller 0xffffffff81169ae3
>
> Any errors in the log before this (e.g. IO errors)?
>
> > Pid: 4022, comm: procmail Not tainted 2.6.31.9 #3
> > Call Trace:
> > [<ffffffff8118edfe>] xfs_error_report+0x3e/0x40
> > [<ffffffff811680fa>] xfs_alloc_fixup_trees+0x2ba/0x340
> > [<ffffffff81167de9>] ? xfs_alloc_get_rec+0x29/0x60
> > [<ffffffff81169ae3>] xfs_alloc_ag_vextent_near+0x3f3/0x940
> > [<ffffffff8116a105>] xfs_alloc_ag_vextent+0xd5/0x130
> > [<ffffffff8116aa68>] xfs_alloc_vextent+0x3a8/0x4f0
> .....
>
> Looks like a corrupted free space tree - that could have happened a
> long time ago and only now are you tripping over it. I'd run
> xfs_repair on the filesystem to fix up the problem. If it happens
> again then we'll have to look deeper.
>
> Cheers,
>
> Dave.
> --
> Dave Chinner
> david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2010-01-06 9:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-12-28 15:10 xfs 2.6.31.9 error DS
2009-12-28 23:22 ` Dave Chinner
2010-01-06 9:02 ` xfs 2.6.31.9 error - possibly SOLVED DS
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox