Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g0HL9k231746 for linux-xfs-outgoing; Thu, 17 Jan 2002 13:09:46 -0800 Received: from tux.rsn.bth.se (tux.rsn.bth.se [194.47.143.135]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g0HL9eP31724 for ; Thu, 17 Jan 2002 13:09:41 -0800 Received: from localhost (gandalf@localhost [127.0.0.1]) by tux.rsn.bth.se (8.12.1/8.12.1/Debian -5) with ESMTP id g0HK90lx026649; Thu, 17 Jan 2002 21:09:00 +0100 Date: Thu, 17 Jan 2002 21:09:00 +0100 (CET) From: Martin Josefsson X-Sender: gandalf@tux.rsn.bth.se To: Steve Lord cc: Wessel Dankers , linux-xfs@oss.sgi.com Subject: Re: Large file I/O error In-Reply-To: <1011294784.13534.695.camel@jen.americas.sgi.com> Message-ID: X-message-flag: Get yourself a real mail client! http://www.washington.edu/pine/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Status: O Content-Length: 963 Lines: 22 On 17 Jan 2002, Steve Lord wrote: > Someone else just pointed out that forced shutdown is overwriting the > super block - which is not good. There appear to be a bunch of dirty > buffers with a zero disk address in them left behind. It is being > worked on. Just have to say that I can confirm this, I had to run xfs_repair after a forced shutdown because of major interruptproblems in the machine so the promise ata-driver complained about irq timeouts all the time... The superblock was overwritten. xfs_repair also complained about other files which were ok before the forced shutdown, and after the shutdown and running xfs_repair they became corrupt. I don't know if this is an possible XFS problem or something caused by the interrupt problems. Those files were written some time before and were possible read from when the forced shutdown occured. /Martin Never argue with an idiot. They drag you down to their level, then beat you with experience.