From: David Chinner <dgc@sgi.com>
To: Marco Berizzi <pupilla@hotmail.com>
Cc: David Chinner <dgc@sgi.com>,
linux-kernel@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: XFS internal error xfs_da_do_buf(2) at line 2087 of file fs/xfs/xfs_da_btree.c. Caller 0xc01b00bd
Date: Sat, 17 Mar 2007 06:59:51 +1100 [thread overview]
Message-ID: <20070316195951.GB5743@melbourne.sgi.com> (raw)
In-Reply-To: <BAY103-DAV13EC09E9BCB3E8C9D5EEA2B2710@phx.gbl>
On Fri, Mar 16, 2007 at 12:05:33PM +0100, Marco Berizzi wrote:
> David Chinner wrote:
>
> > can
> > you post a url to the commit?
>
> http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.19.y.git;a=commit;h=7fbbb01dca7704d52ace6f45a805c98a5b0362f9
Ok, so an ipsec change. And I see from the history below it
really has nothing to do with this problem. it seems the problem
has something to do with changes between 2.6.19.1 and 2.6.19.2.
There were no changes to XFS between 2.6.19.1 and 2.6.19.2,
so I'm thinking that your problems are related to something
other than XFS. Can you do a git bisect to determine what the
bad patch is?
> > Can you run xfs_repair on that filesystem and see if reports
> > (and fixes) any problems?
>
> I don't need to run xfs_repair to fix the problem,
Except that the trigger might be on-disk corruption so we
need to rule that out first.
> I only unplug the power cable and reboot the system,
> xfs filesystem are correctly mounted.
> However tell me if I must run xfs_repair to check
> the filesystem.
Yes, you need to run xfs_repair.
Cheers,
Dave.
--
Dave Chinner
Principal Engineer
SGI Australian Software Group
next prev parent reply other threads:[~2007-03-16 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BAY103-DAV1066400DF0615AD677EA1B2730@phx.gbl>
2007-03-16 1:25 ` XFS internal error xfs_da_do_buf(2) at line 2087 of file fs/xfs/xfs_da_btree.c. Caller 0xc01b00bd David Chinner
[not found] ` <BAY103-DAV13EC09E9BCB3E8C9D5EEA2B2710@phx.gbl>
2007-03-16 19:59 ` David Chinner [this message]
2007-03-17 13:00 ` Marco Berizzi
[not found] ` <BAY103-DAV9C465F21C87A900314523B2760@phx.gbl>
2007-03-20 6:46 ` David Chinner
2007-06-07 7:44 ` Marco Berizzi
2007-06-07 13:05 ` David Chinner
2007-06-08 13:59 ` Marco Berizzi
2007-06-12 6:14 ` David Chinner
2007-06-12 7:14 ` Marco Berizzi
2007-06-19 10:36 ` Marco Berizzi
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=20070316195951.GB5743@melbourne.sgi.com \
--to=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pupilla@hotmail.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