public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: Jan De Luyck <lkml@kcore.org>
Cc: linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: [2.6.10-rc2] XFS filesystem corruption
Date: Mon, 22 Nov 2004 07:51:06 -0800	[thread overview]
Message-ID: <20041122155106.GG2714@holomorphy.com> (raw)
In-Reply-To: <200411221530.30325.lkml@kcore.org>

On Mon, Nov 22, 2004 at 03:30:29PM +0100, Jan De Luyck wrote:
> [resend with correct email address for LKML]
> [Please CC all answers from linux-xfs to me, since I'm not subscribed on that list]
> Yesterday I encountered an on-the-fly corruption of my /home filesystem. It worked perfectly one second, the next I hit these nice errors:
> Nov 21 16:37:22 precious kernel: 0x0: 31 9e ce 63 cf ff 9c cf ff 31 61 63 ff ff ff ff 
> Nov 21 16:37:23 precious kernel: Filesystem "hda5": XFS internal error xfs_da_do_buf(2) at line 2273 of file fs/xfs/xfs_da_btree.c.  Caller 0xc01fb908
> Nov 21 16:37:23 precious kernel:  [xfs_da_do_buf+905/2160] xfs_da_do_buf+0x389/0x870

I don't have any ideas at the moment, but please cc: me also. I'd like
to watch for issues I do understand as this bug's nature is clarified.


-- wli

  reply	other threads:[~2004-11-22 16:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-22 14:30 [2.6.10-rc2] XFS filesystem corruption Jan De Luyck
2004-11-22 15:51 ` William Lee Irwin III [this message]
2004-11-23 10:13   ` Prakash K. Cheemplavam
2004-11-23 19:13     ` Lee Revell
2004-11-23 19:22       ` Prakash K. Cheemplavam
2004-11-23 21:27     ` Nathan Scott
2004-11-24  8:04       ` Prakash K. Cheemplavam
2004-11-24 12:50         ` Eric Sandeen
2004-11-25  7:28           ` Prakash K. Cheemplavam
2004-11-22 23:34 ` Eric Sandeen
2004-11-23  6:36   ` Jan De Luyck

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=20041122155106.GG2714@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-xfs@oss.sgi.com \
    --cc=lkml@kcore.org \
    /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