From: Dave Chinner <david@fromorbit.com>
To: "Sławomir Nowakowski" <nailman23@gmail.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS on 2.6.25.17 kernel issue
Date: Fri, 3 Oct 2008 18:34:14 +1000 [thread overview]
Message-ID: <20081003083414.GM30001@disturbed> (raw)
In-Reply-To: <50ed5c760810022334j69befdb9pa0bf5ec29aad9126@mail.gmail.com>
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@fromorbit.com
next prev parent reply other threads:[~2008-10-03 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 6:34 XFS on 2.6.25.17 kernel issue Sławomir Nowakowski
2008-10-03 8:34 ` Dave Chinner [this message]
2008-10-03 9:34 ` Sławomir Nowakowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081003083414.GM30001@disturbed \
--to=david@fromorbit.com \
--cc=nailman23@gmail.com \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox