Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id g06LdBp18148 for linux-xfs-outgoing; Sun, 6 Jan 2002 13:39:11 -0800 Received: from coredump.sh0n.net (qmailremote@CPEdeadbeef0000.cpe.net.cable.rogers.com [24.100.234.67]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id g06Ld5g18126 for ; Sun, 6 Jan 2002 13:39:05 -0800 Received: (qmail 6862 invoked from network); 6 Jan 2002 20:39:50 -0000 Received: from coredump.sh0n.net (sh0n@24.100.234.67) by coredump.sh0n.net with SMTP; 6 Jan 2002 20:39:50 -0000 Date: Sun, 6 Jan 2002 15:39:49 -0500 (EST) From: Shawn Starr To: Stephen Lord cc: linux-xfs@oss.sgi.com Subject: Re: XFS fails fsx-linux.c (1 charactor difference) In-Reply-To: <3C38B3B7.3070000@sgi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-linux-xfs@oss.sgi.com Precedence: bulk Status: O Content-Length: 1006 Lines: 44 sure: http://www.codemonkey.org.uk/cruft/fsx-linux.c Shawn. On Sun, 6 Jan 2002, Stephen Lord wrote: > Shawn Starr wrote: > > >With an exaustive test running overnight with the new -mjc branch of 2.4 > >(I'm working on getting XFS into the branch) I noticed the following > >fault: > > > >truncating to largest ever: 0x3fcb9 > >READ BAD DATA: offset = 0x53e5, size = 0x9c0a > >OFFSET GOOD BAD RANGE > >0x 9000 0x0000 0x0101 0x 5faa > >operation# (mod 256) for the bad data may be 1 > >LOG DUMP (1145 total operations): > > > >I have attached the dump of the results run and the binary difference is > >ONE charactor: > > > >cmp boom boom.fsxgood > >boom boom.fsxgood differ: char 10428, line 18 > > > >It would be a good idea to use the fsx-linux.c program to stress test XFS. > >The fsx-linux program has found several bugs in NFS and other filesystems. > > > >Shawn. > > > Google does not have any references to this program - can you provide a > pointer? > > Thanks > > Steve > > > > >