mkfs under 386/ix
Paul Gillingwater
paul at actrix.gen.nz
Tue Dec 4 19:04:53 AEST 1990
Yesterday I had to rebuild a file system on our 386/ix 2.02 system
for the second time. The file system is mounted as /usr/spool/news,
and needed about 10,000 more inodes. :-)
The problem: the standard ISC docs donfor 2.02 't have a mkfs man page.
The man pages I could find were different (from non-ISC source).
I couldn't work out how big the file system originally was, in
blocks, because I'd lost the mkfs.data that was originally created.
How should one find this out? Specifically, how can I empirically
establish the total size available for an EXISTING section (I won't
call it a partition, because several sections may share the same
entry in the partition table which is accessed by fdisk).
My concern is that when i used
mkfs /dev/dsk/0s3 117000:28000 1 2048
I got exactly the size in blocks that I requested. My worry is that
I don't know how big it could be before it starts to overlap onto
the next disk section.
I chose 117000 because it was somewhat less than the original size
on blocks for the section. 28000 is the new number of inodes,
necessary for a healthy news feed here. 1 is the inter-sector gap I
think -- we're using an ESDI controller for this drive. 2048 -- I
wasn't sure whether this should be something else...
--
Paul Gillingwater, paul at actrix.gen.nz
More information about the Comp.unix.sysv386
mailing list