xfs
[Top] [All Lists]

Re: XFS fails fsx-linux.c (1 charactor difference)

To: Stephen Lord <lord@xxxxxxx>
Subject: Re: XFS fails fsx-linux.c (1 charactor difference)
From: Shawn Starr <spstarr@xxxxxxxx>
Date: Sun, 6 Jan 2002 17:09:44 -0500 (EST)
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <3C38BD16.9020704@xxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
[root@coredump src]# ./blowup-xfs boom
truncating to largest ever: 0x13e76
truncating to largest ever: 0x2e52c
truncating to largest ever: 0x3c2c2
truncating to largest ever: 0x3f15f
truncating to largest ever: 0x3fcb9
truncating to largest ever: 0x3fe96
truncating to largest ever: 0x3ff9d
truncating to largest ever: 0x3ffff
skipping zero size read
skipping zero size write


Running the program again, with today's XFS changes my tree was a little
out of date.. so far it hasn't blown up yet ;-)

Shawn.

On Sun, 6 Jan 2002, Stephen Lord wrote:

> Shawn Starr wrote:
>
> >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
> >>
> >>
> >>
> >>
> >>
> Ah ha, I have seen this program before (under a slightly different name)
> it was running just fine
> on XFS when I last ran it. On the other hand we appear to be suffering
> from a regression
> right now, and if I am correct, the regression happened right around the
> day I last ran
> this program, so it is possible the same change broke fsx as well as
> emacs builds....
>
> Steve
>
>
>
>
>


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