Received: from oss.sgi.com (localhost [127.0.0.1]) by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g4MCxXnC005893 for ; Wed, 22 May 2002 05:59:33 -0700 Received: (from majordomo@localhost) by oss.sgi.com (8.12.3/8.12.3/Submit) id g4MCxX6u005892 for linux-xfs-outgoing; Wed, 22 May 2002 05:59:33 -0700 X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-linux-xfs@oss.sgi.com using -f Received: from zeus-e8.americas.sgi.com ([198.149.7.250]) by oss.sgi.com (8.12.3/8.12.3) with SMTP id g4MCxRnC005864 for ; Wed, 22 May 2002 05:59:27 -0700 Received: from poppy-e185.americas.sgi.com (poppy-e185.americas.sgi.com [128.162.185.207]) by zeus-e8.americas.sgi.com (SGI-SGI-8.9.3/americas-smart-nospam1.1) with ESMTP id IAA79041; Wed, 22 May 2002 08:00:18 -0500 (CDT) Received: from stout.americas.sgi.com (stout.americas.sgi.com [128.162.187.5]) by poppy-e185.americas.sgi.com (980427.SGI.8.8.8/SGI-server-1.7) with ESMTP id IAA50528; Wed, 22 May 2002 08:00:17 -0500 (CDT) Date: Wed, 22 May 2002 08:00:23 -0500 (CDT) From: Eric Sandeen X-X-Sender: sandeen@stout.americas.sgi.com To: Michael Wahlbrink cc: linux-xfs Subject: Re: Still some corruption occurs on my root filesystem In-Reply-To: <3CEB6FF4.3040305@propack-data.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk On Wed, 22 May 2002, Michael Wahlbrink wrote: > Hi, > Got the data back with the xfs_progs from cvs. > > All works fine with disabled writecache on the IDE HDDs, untill I saw a > few reboots later that there was corruption on my root fs again :-(. > This corruption will not cause the system to hang, but ...... you know.... > > here's a snippet from my log: The only thing here is "normal" log recovery, nothing that should indicate corruption. I assume that this is after what claims to be a clean shutdown? > And what about the "Invalid ioctl" messages I get aometimes since I use xfs? Probably the BLKSETSIZE ioctl, perhaps your raid driver doesn't implement it? I wonder if this could be part of the problem... at one point it looked like this was harmless. -Eric