Date: Sun, 26 Dec 1999 19:30:03 -0800 (PST) From: "Wes Bauske" <wsb@paralleldata.com> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/15611: EIDE Large Disk Support, Newfs problem, File systemcorruption,IBM-DPTA-353750 Message-ID: <199912270330.TAA96624@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/15611; it has been noted by GNATS. From: "Wes Bauske" <wsb@paralleldata.com> To: mjacob@feral.com Cc: mjacob@FreeBSD.org, FreeBSD-gnats-submit@FreeBSD.org, rjbubon@bigi.com Subject: Re: kern/15611: EIDE Large Disk Support, Newfs problem, File systemcorruption,IBM-DPTA-353750 Date: Sun, 26 Dec 1999 21:16:55 -0600 Matthew Jacob wrote: > > On Sun, 26 Dec 1999, Wes Bauske wrote: > > > Matt, > > > > OK. I assume you also wrote some significant files onto it?? > > I wrote a 2GB file for testing. > > Nope, I'm a conehead- I only created/fsck'd it. I really didn't have time > to do exhaustive testing. > OK. But it would be good to try put a file or two on it. > > > > The file system does create most of the time. It's only when > > you start writing data to it that there's trouble. Also, if > > What I had heard was that there was a problem > 32GB in creating the > filesystem. I checked that this seemed to work in -current. > Yes. That's what I meant by "most of the time". It will sometimes just reboot on it's own while creating the FS. That in itself doesn't cause the root FS corruption though. > > your single file system works, then it may be something to > > do with my layout. To recap, I have 2 slices, one is 1GB > > with 128MB swap, and the rest root(/) and the other slice > > contains a single FS of around 38GB as work space for my > > application. > > > > I'm running pure 3.3 from the Walnut Creek CD, no updates. > > > Also, what about forcing the driver to use LBA mode? I tried > > It does. It was just sysinstall that said, "Hmm- looks odd!"... > > > Get's tiring to reinstall the OS after each test. > > Well, yes. But all I did was give this a try under -current- seemed to > work with the newest ata driver (no special flags)- probably works even > for files on it. > > I think I'm gently suggeting that you shouldn't hold FreeBSD to a higher > standard than Linux. I'm giving you a standard linux answer of- "try the > latest kernel"- in this case, do a net install of -current and see if this > solves your problems. Right now I can't due to heavy downloading of RH6.1 iso images. I should be done with that in a day or two at which point I'll see about continuing testing, including trying what's on the net instead of the CD. I assume I'll have to create floppies for that since I'm currently booting directly from the 3.3 CD. > > The problems may or may not be fixed in 3.4 (which is the latest -stable > release- just cut, too late to fix for this problem if it still is a > problem for 3.X), but you seem sophisticated enough to try the -current > netinstall to see if it solves your problems. If it's still a problem in > 3.X FreeBSD it will probably get fixed, but everyone's pretty focussed on > closing off 4.0. > > -matt I'll let you know what I find. Wes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199912270330.TAA96624>