Received:  by oss.sgi.com id <S554115AbRBVMAe>;
	Thu, 22 Feb 2001 04:00:34 -0800
Received: from jeremi.jeremi.pl ([212.160.232.2]:34747 "EHLO jeremi.jeremi.pl")
	by oss.sgi.com with ESMTP id <S554112AbRBVMAN>;
	Thu, 22 Feb 2001 04:00:13 -0800
Received: from jeremi.pl (nobody@localhost [127.0.0.1])
	by jeremi.jeremi.pl (8.10.1/8.10.1) with SMTP id f1MDvM007190
	for <linux-xfs@oss.sgi.com>; Thu, 22 Feb 2001 14:57:22 +0100
Received: from 212.160.232.6
        (SquirrelMail authenticated user linux-xfs)
        by mail.jeremi.pl with HTTP;
        Thu, 22 Feb 2001 14:57:22 +0100 (CET)
Message-ID: <1460.212.160.232.6.982850242.squirrel@mail.jeremi.pl>
Date:   Thu, 22 Feb 2001 14:57:22 +0100 (CET)
Subject: Hardware fault intolerance...
From:   "Irresponsible & Crazy" <linux-xfs@jeremi.pl>
To:     linux-xfs@oss.sgi.com
X-Mailer: SquirrelMail (version 1.0pre2)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-2
Content-Transfer-Encoding: 8bit
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk
Return-Path: <owner-linux-xfs@oss.sgi.com>
X-Orcpt: rfc822;linux-xfs-outgoing

Does anybody know how xfs handles "just appeared" badblocks? If even...
How to inform xfs about badblocks (if that's possible) to let xfs avoid them
or just kiss hdd goodbye

I took latest cvs snapshot (21.02.2001 18:00CET), made kernel and set vga=9
to see whole Oops output and I think I know where exactly those bads hide on
my hdd, I should have Oops in my next post if anybody interested...

Filip
-- 
"Oh shit! o shit! o shit! I'm gonna die! I'm gonna die!" - Rincewind