Date: Sat, 4 Mar 2000 07:56:54 -0500 From: "Ben Goodwin" <ben-lists@atomicmatrix.net> To: <freebsd-questions@freebsd.org> Subject: 34GB+ hard drives and FreeBSD 3.4 - doesn't work! Message-ID: <005401bf85d9$1e232380$6a477392@dsg.atomicmatrix.net>
next in thread | raw e-mail | index | archive | help
This is a multi-part message in MIME format.
------=_NextPart_000_0051_01BF85AF.3523E8A0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I *know* I saw a message in one of these lists some time back stating =
that there was a problem with the ATAPI/IDE driver in FreeBSD 3.4 (but =
not in 4.0) with disks around the 34 GB mark. Of course I didn't read =
it then cuz I didn't have anything of that nature, but now I do. I have =
some 40 GB drives, and I can't access all the space w/out crashing the =
system. I had hoped the problem would be patched so I cvsup'ed the =
kernel to -stable but no such luck. Is there a workaround/patch?
I've tried many times to search the mailing lists but I just can't find =
anything (except a coupel other people asking basically the same =
question)
To be specific about the problem, I'm vinum-concat'ing these drives =
together. If I label the disks to 60,000 sectors, all works well. When =
I tried 680000 sectors, it newfs'ed fine, but when I mounted the =
resulting filesystem, I couldn't see anything with an ls -la (not even =
"." or "..") and any attempts to write to the filesystem (regardless of =
whether I had permission to do so) the o/s would crash. This is with =
both 3.4R and 3.4S as of yesterday. It's not a problem with too big a =
filesystem - as I've concat'ed 3 60,0000-sector pieces together just =
fine, but couldn't mess with a 2-disk 68,000 sector setup ...
TIA,
-=3D| Ben
------=_NextPart_000_0051_01BF85AF.3523E8A0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I *know* I saw a message in one of =
these lists some=20
time back stating that there was a problem with the ATAPI/IDE driver in =
FreeBSD=20
3.4 (but not in 4.0) with disks around the 34 GB mark. Of course I =
didn't=20
read it then cuz I didn't have anything of that nature, but now I =
do. I=20
have some 40 GB drives, and I can't access all the space w/out crashing =
the=20
system. I had hoped the problem would be patched so I cvsup'ed the =
kernel=20
to -stable but no such luck. Is there a =
workaround/patch?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>I've tried many times to search the =
mailing lists=20
but I just can't find anything (except a coupel other people asking =
basically=20
the same question)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>To be specific about the problem, I'm=20
vinum-concat'ing these drives together. If I label the disks to =
60,000=20
sectors, all works well. When I tried 680000 sectors, it newfs'ed fine, =
but when=20
I mounted the resulting filesystem, I couldn't see anything with an ls =
-la (not=20
even "." or "..") and any attempts to write to the filesystem =
(regardless of=20
whether I had permission to do so) the o/s would crash. This is =
with both=20
3.4R and 3.4S as of yesterday. It's not a problem with too big a=20
filesystem - as I've concat'ed 3 60,0000-sector pieces together just =
fine, but=20
couldn't mess with a 2-disk 68,000 sector setup ...</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2>TIA,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT face=3DArial size=3D2> -=3D| =
Ben</FONT></DIV>
<DIV> </DIV></BODY></HTML>
------=_NextPart_000_0051_01BF85AF.3523E8A0--
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?005401bf85d9$1e232380$6a477392>