Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: 2.4: "access beyond end of device" after ext2 mount
Date: Tue, 18 Jan 2005 10:07:27 -0500
Message-ID: <2E314DE03538984BA5634F12115B3A4E01BC42B5@email1.mitretek.org>
Thread-Topic: 2.4: "access beyond end of device" after ext2 mount
thread-index: AcT9bwbTYXadNnGgRKmfhXUgqlvuvAAAFWfw
From: "Piszcz, Justin Michael" <justin.piszcz@mitretek.org>
To: "Andries Brouwer" <aebr@win.tue.nl>
Cc: "Mario Holbe" <Mario.Holbe@TU-Ilmenau.DE>, <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1073
Lines: 26

Not trying to spread FUD, I am just explaining I had the same issue and
that was the resolution.

-----Original Message-----
From: Andries Brouwer [mailto:aebr@win.tue.nl] 
Sent: Tuesday, January 18, 2005 10:04 AM
To: Piszcz, Justin Michael
Cc: Mario Holbe; linux-kernel@vger.kernel.org
Subject: Re: 2.4: "access beyond end of device" after ext2 mount

On Tue, Jan 18, 2005 at 09:24:03AM -0500, Piszcz, Justin Michael wrote:

> Is the problem with the drive on the promise board or the drive on the
> VIA chipset?

Oh, please - no FUD. There is no problem, and we understand in detail
what happens and why it happens. There is no need for any speculation.
There is no relation to disk hardware or indeed any hardware.

> Did you check your HDD manual to see if you have
> the 32GB clip enabled?  If so, you need to disable this.
-
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/