Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!zardoz.cpd.com!everex!jde From: jde@everex.uucp (-Jeff Ellis()) Newsgroups: comp.unix.sysv386 Subject: Re: RLL and ESIX Message-ID: <1990Nov19.184520.20307@everex.uucp> Date: 19 Nov 90 18:45:20 GMT References: <1990Nov13.142439.155@cimcor.mn.org> Organization: ESIX Computers, Inc. Lines: 19 In article <1990Nov13.142439.155@cimcor.mn.org> mike@cimcor.mn.org (Michael Grenier) writes: >When installing ESIX and you have a big non-scsi drive, you must set >partitions evenly if you are going to use FFS. It seems that the >Fast File System will go right ahead and create a file system with more >than 64K inodes. This is bad in System V which uses an unsigned short >to hold the inode number in the kernel and will cause the kernel >to panic when mounting the file system. Scsi installation checks for the >above condition. ESIX technical support admits to the problem. I have talked with the Guy that did the work on the newfs commandand we looked at the source code. In ESIX Rev D beta we had a problem when using large SCSI drives, newfs (called by mkfs) could make FFS file systems that had more 64k inodes and panic the system. But it was fixed before it went into production and the newfs command checks for that condition and keeps it less than 64k. This works for all type of drives, not just SCSI. -- Jeff Ellis ESIX SYSTEM/V UUCP:uunet!zardoz!everex!jde US Mail: 1923 St. Andrew Place, Santa Ana, CA 92705