Return to BSD News archive
Newsgroups: comp.unix.bsd.bsdi.misc
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.vbc.net!vbcnet-west!knews.uk0.vbc.net!vbcnet-gb!azure.xara.net!xara.net!dispatch.news.demon.net!demon!news.sprintlink.net!news-peer.sprintlink.net!news.mathworks.com!cam-news-hub1.bbnplanet.com!news.bbnplanet.com!cam-news-feed5.bbnplanet.com!cass.ma02.bull.com!steamer.clam.com!spdcc!dyer
From: dyer@spdcc.com (Steve Dyer)
Subject: Maxtor 5.1gb problem: resolution
Message-ID: <E7no5p.Ko7@spdcc.com>
Organization: S.P. Dyer Computer Consulting, Cambridge MA
Date: Wed, 26 Mar 1997 14:56:13 GMT
Lines: 27
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:6463
I suppose I should mention here (since no one fron BSDI has)
that the problem I was having with data corruption on a
partition larger than 4gb on the Maxtor 5.1gig disk was
due to a bug in the IDE driver, wd.c. Not surprising,
since it wasn't until the Maxtor came out that you could
have a disk partition on an IDE disk that large. Thanks
to Chris Torek for the following:
This looks like a bug in the IDE driver. If you have source,
find the line in wdstart that reads:
du->wd_blknum = bp->b_blkno * DEV_BSIZE / du->wd_dd.d_secsize;
and try (as a quick patch):
du->wd_blknum = (u_quad_t)bp->b_blkno * DEV_BSIZE / du->wd_dd.d_secsize;
This isn't an official patch, just a suggestion for me to try, but
it seems to be working nicely.
This was in BSDI 2.1. I don't know about BSDI 3.0, though
it wouldn't surprise me if it were still in there.
--
Steve Dyer
dyer@ursa-major.spdcc.com