Subject: Re: Annoying panics...
To: The Great Mr. Kurtz [David A. Gatwood] <davagatw@Mars.utm.edU>
From: Colin Wood <cwood@ichips.intel.com>
List: port-mac68k
Date: 08/10/1997 13:33:09
The Great Mr. Kurtz [David A. Gatwood] wrote:

> On Sun, 10 Aug 1997, Colin Wood wrote:
> 
> > ADAMGOOD@delphi.com wrote:
> > 
> > > When I did a 'df' on it (before 'fsck'ing) it showed that several
> > > hundred thousand blocks had already been allocated, but I had just 'newfs'ed
> > > it from the Mac side.  Hmmm . . .  I 'newfs'ed it again from the BSD side,
> > > and this time 'df' showed that the partition was indeed empty.
> > 
> > Kinda strange....did you run 'fsck' and then look, or did you just go and
> > 'newfs' it?
> 
> <snip>
> 
> > > Oh, one thing I forgot - in addition to the mount root/not clean problem,
> > > when I try to use the installer on that disk, and I do an 'ls' it says
> > > something about bad inodes and dies.  Not a good sign, but that doesn't
> > > happen once I'm in BSD, so I used 'hfs' to copy all the tarballs to the
> > > BSD side and installed them from there.
> > 
> > Hmmm....bad inode or no such inode?  I get some kind of "no such file"
> > type error all the time in the Installer, but it doesn't crash...I'd
> > recommend using hfs anyway, though.  It's _alot_ faster than the
> > Installer.
> 
> I get this too, but only on the partition that I newfs'ed from the NetBSD
> side.  I think NetBSD's newfs must default to the newer level 2 (I think
> that's the right number) filesystems, which the installer doesn't support
> at this time.  (Perhaps the default should be changed until such time as
> it does?)  If you use newfs, try specifying the filesystem revision level
> on the command line (man newfs for details).  Of course that's only
> speculation, there could easily be other reasons, that just seems the most
> likely guess.

Ah, yes!  I had forgotten about that.  The level 2 ffs created by newfs is
incompatible with the installer...something else to go into the FAQ if
it's not already there ;-)  As for changing the default, since newfs is
pretty much architecture independent, I'm not too sure they other ports
would like us messing with their newfs ;-)

Later.

-- 
Colin Wood                                 cwood@ichips.intel.com
Component Design Engineer - MD6                 Intel Corporation
-----------------------------------------------------------------
I speak only on my own behalf, not for my employer.