xfs
[Top] [All Lists]

Re: linux software RAID, 2.6.6, XFS, Postgres: corrupt files

To: Ian Westmacott <ianw@xxxxxxxxxxxxxx>, "Thomas J. Teixeira" <tjt@xxxxxxxxxxxxxx>
Subject: Re: linux software RAID, 2.6.6, XFS, Postgres: corrupt files
From: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 18 Apr 2005 15:00:23 +1000
Cc: linux-xfs <linux-xfs@xxxxxxxxxxx>
In-reply-to: <1113594280.9697.103.camel@vishambu.intellivid.com>
References: <1113594280.9697.103.camel@vishambu.intellivid.com>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.3i
Hi there,

On Fri, Apr 15, 2005 at 03:44:41PM -0400, Thomas J. Teixeira wrote:
> Resending this since it didn't seem to go through the first time -- I'm
> looking for kernel diagnostic tools.

KDB is the tool we use for this sort of work.  Get it from XFS CVS,
where there is also XFS extensions for interpreting and dumping out
XFS specific data structures.  The current CVS revision is unlikely
to work on 2.6.6 though, since its moved on from then, but you may
be able to coerce CVS into extracting the right version if you must
use 2.6.6.

Your post reminded me of another fix - if you are on 2.6.6 you will
likely not have this... (see xfs_aops.c CVS revision history)

date: 2004/09/30 01:37:19;  author: nathans;  state: Exp;  lines: +19 -12
modid: xfs-linux-melb:xfs-kern:19622a
Fix sync issues - use correct writepage page re-dirty interface, and do
not clear dirty flag if page only partially written.

IIRC, that was merged in 2.6.9 (but don't quote me on that, it was
awhile ago).

This may well resolve the issue you're seeing, it resolved all the
known data sync problems at the time, although there now seems to be
a harder-to-hit issue that I'm working through with Rich and James.

cheers.

-- 
Nathan


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