From: Christoph Hellwig <hch@infradead.org>
To: Adam Nielsen <a.nielsen@shikadi.net>
Cc: LKML Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: XFS internal error xfs_da_do_buf(1) at line 2015 of file fs/xfs/xfs_da_btree.c
Date: Sun, 4 Jan 2009 02:46:59 -0500 [thread overview]
Message-ID: <20090104074659.GA16775@infradead.org> (raw)
In-Reply-To: <49600DE6.2080108@shikadi.net>
On Sun, Jan 04, 2009 at 11:16:22AM +1000, Adam Nielsen wrote:
> Hi all,
>
> I'm having a recurring problem with XFS which started about a day ago.
> All of a sudden when reading a certain part of the disk (not sure where,
> but my nightly backups trigger it) I get an infinite loop of these
> messages appearing in my logs:
>
> xfs_da_do_buf: bno 8388608
> dir: inode 3087268096
> Filesystem "md0": XFS internal error xfs_da_do_buf(1) at line 2015 of
> file fs/xfs/xfs_da_btree.c. Caller 0xffffffff802eba63
> Pid: 4445, comm: metalog Tainted: P 2.6.28-rc2 #3
This is a typical result of a power loss scenario with write caches
enabled and without barriers. Given that md can't pass through barriers
did you disable the write caches on your disk?
> Does anyone know what this error means? Do I need to reformat the filesystem?
Run xfs_repair over it to fix up the directory, and make sure to
configure your disks properly so that it doesn't happen again..
next prev parent reply other threads:[~2009-01-04 7:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 1:16 XFS internal error xfs_da_do_buf(1) at line 2015 of file fs/xfs/xfs_da_btree.c Adam Nielsen
2009-01-04 7:46 ` Christoph Hellwig [this message]
2009-01-04 9:03 ` Adam Nielsen
2009-01-04 9:23 ` Christoph Hellwig
2009-01-04 11:44 ` Alan Cox
2009-01-04 15:34 ` Christoph Hellwig
2009-01-04 15:50 ` Andi Kleen
2009-01-05 5:12 ` markus reichelt
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=20090104074659.GA16775@infradead.org \
--to=hch@infradead.org \
--cc=a.nielsen@shikadi.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.