Subject: Re: ext3 fsx failures on 2.6.19-rc1
From: Badari Pulavarty <pbadari@us.ibm.com>
To: Jan Kara <jack@suse.cz>
Cc: akpm@osdl.org, esandeen@redhat.com, ext4 <linux-ext4@vger.kernel.org>,
       lkml <linux-kernel@vger.kernel.org>, Dave Jones <davej@redhat.com>
In-Reply-To: <20061010123059.GJ23622@atrey.karlin.mff.cuni.cz>
References: <1160436605.17103.27.camel@dyn9047017100.beaverton.ibm.com>
	 <20061010123059.GJ23622@atrey.karlin.mff.cuni.cz>
Content-Type: text/plain
Date: Tue, 10 Oct 2006 09:41:27 -0700
Message-Id: <1160498487.17103.30.camel@dyn9047017100.beaverton.ibm.com>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1190
Lines: 37

On Tue, 2006-10-10 at 14:30 +0200, Jan Kara wrote:
>   Hi,
> 
> > I am having fsx failures on 2.6.19-rc1.
>   :(
> 
> > I don't have any useful information at this time to track it down.
> > I am running 4 copies of fsx (+ fsstress) on a 1k filesystem and
> > one copy of fsx dies.
>   How long does it take? 

Random. It happens any where from 1 hours to 6 hours.

> 
> > fsx-linux[20667]: segfault at 00000000ffffffff rip 00002af0fe031690 rsp
> > 00007fffacc03b88 error 4
> > 
> > READ BAD DATA: offset = 0xa352, size = 0x5fef
> > OFFSET  GOOD    BAD     RANGE
> > 0x df90 0x48e4  0x0000  0x   70
> > operation# (mod 256) for the bad data unknown, check HOLE and EXTEND ops
>   Hmm, so fsx-linux wrote something and read back zeros. Strange. Do you
> know what that 'segfault' message means? I cannot find it in my copy of
> fsx-linux...
> 
> 							
fsx got a segmentation fault and died. These are the messages in the
dmesg.

Thanks,
Badari

-
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/