Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!qns3.qns.net!imci4!newsfeed.internetmci.com!news.mathworks.com!uunet!in3.uu.net!myname.my.domain!jons7500.vc.net!user From: jon@vcnet.com (Jon Rust) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Big news drive = crash? Date: Mon, 29 Jul 1996 11:03:34 -0700 Organization: Internet Access of Ventura County 805.383.3500 Lines: 17 Message-ID: <jon-2907961103340001@jons7500.vc.net> NNTP-Posting-Host: jons7500.vc.net X-Newsreader: Yet Another NewsWatcher 2.1.2 Is there an inode and/or file limit that would cause FreeBSD's kernel to panic? I'm running INN 1.4unoff4 and I've got a mix of 4 gig and 2 gig drives. On my linux machine, I had to partition the crap out of those drives because it had an inode limit of 1.5 million. However, someone told me FreeBSD wouldn't have the same problem. The 2 gigs and the 4 gig aren't partitioned. I've checked all the drives using fsck and the Adaptec BIOS verify command. When it crashes it just says someting about a bad directory, the kernel is in a panic, later... After these crashes fsck reports a few problems, but says it's fixed em. I've tried reformatting and creating a new system on the drives, but it's no good. Anyhelp would be much appreciated. Since I can't keep my news machine alive for even a day, please respond via email if at all possible. Jon