From: Neil Brown <neilb@cse.unsw.edu.au>
To: "Robert L. Harris" <Robert.L.Harris@rdlg.net>
Date: Wed, 30 Jul 2003 14:29:23 +1000
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <16167.18851.734177.14074@gargle.gargle.HOWL>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: NFS Server running 2.6.0-test2
In-Reply-To: message from Robert L. Harris on Tuesday July 29
References: <20030729110716.GC786@rdlg.net>
	<16166.25350.70923.742360@gargle.gargle.HOWL>
	<20030729130924.GE786@rdlg.net>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1291
Lines: 33

On Tuesday July 29, Robert.L.Harris@rdlg.net wrote:
> 
> 
> The messages file is completely empty of any error messages related to
> anything disk or filesystem related from about 6 hours prior to the
> error up until the time I rebooted.  In addition the actual device
> (RAID5 filesystem) is intact.
> 

Well, it looks quite unplesant then.
That error message can only get printed if the JFS_ABORT flag is set
for the ext3 journal, and whenever JFS_ABORT is set, the message:
   Aborting journal on device ...
comes first.  If you don't have that message, then the impossible has
happened.

The impossible is usually caused either by bad memory (and a
single-bit-error in memory could have caused this probem), or by some
stray pointer corrupting something.

So, I would suggest memtest86 if that is convenient, followed by
reporting the problem to the ext3 developers (see the MAINAINERS
file). 

This problem is unlikely to be related to the machine being an NFS
server, though until we know the cause, nothing should be ruled out.

NeilBrown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/