xfs
[Top] [All Lists]

Re: XFS on 2.6.25.17 kernel issue

To: Sławomir Nowakowski <nailman23@xxxxxxxxx>
Subject: Re: XFS on 2.6.25.17 kernel issue
From: Dave Chinner <david@xxxxxxxxxxxxx>
Date: Fri, 3 Oct 2008 18:34:14 +1000
Cc: xfs@xxxxxxxxxxx
In-reply-to: <50ed5c760810022334j69befdb9pa0bf5ec29aad9126@xxxxxxxxxxxxxx>
Mail-followup-to: Sławomir Nowakowski <nailman23@xxxxxxxxx>, xfs@xxxxxxxxxxx
References: <50ed5c760810022334j69befdb9pa0bf5ec29aad9126@xxxxxxxxxxxxxx>
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Oct 03, 2008 at 08:34:52AM +0200, Sławomir Nowakowski wrote:
> Dear All,
> 
> We use kernel 2.6.25.17, Promise STEX 8650 RAID controller, LVM2 and
> snapshots. After about 3 hours of working (using SAMBA, RSYNC etc)
> dmesg showed following errors:
> 
> XFS internal error XFS_WANT_CORRUPTED_GOTO at line 1546 of file
> fs/xfs/xfs_alloc.c.  Caller 0xc024f387
> Pid: 16557, comm: smbd Not tainted 2.6.25.17-oe32-00000-g553425c #18
>  [<c024e15e>] xfs_free_ag_extent+0x2fe/0x670
>  [<c024f387>] xfs_free_extent+0xc7/0xf0
>  [<c024f387>] xfs_free_extent+0xc7/0xf0

Freespace btree corruption. Run xfs_repair on tへe filesystem
to fix the corruption, upgrade to 2.6.27 when it is released to
get all the fixes for known corruptions.

FWIW, I see iSCSI and DRBD are in use on your machine. In the past,
XFS on top of either of these two transports would randomly suffer
from freespace btree corruptions which were not reproducable on
normal local block devices. So the cause of your problem may not be
XFS at all....

Cheers,

Dave.
-- 
Dave Chinner
david@xxxxxxxxxxxxx

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