Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!haven!adm!cmcl2!polyof!john
From: john@polyof.UUCP ( John Buck )
Newsgroups: comp.sys.att
Subject: Re: mkfs and inodes
Summary: mkfs wipes out old inode table
Keywords: 3b2/400; SV R3.1
Message-ID: <440@polyof.UUCP>
Date: 23 Feb 89 18:46:59 GMT
References: <617@mccc.UUCP>
Distribution: na
Organization: Polytechnic University, Farmingdale NY
Lines: 20

In article <617@mccc.UUCP>, pjh@mccc.UUCP (peter j holsberg) writes:
> If I run a mkfs on an existing file system (just to increase the number
> of inodes), will I be wiping out the files in the system?

YES!!! Please back-up your entire file-system BEFORE running mkfs on it.  "mkfs"
will zero any inodes there are currently on the disk, and will extend the
the inode table into space previously used for file data.

> If so, is it necessary to reformat before using mkfs?
> Pete

You do not have to reformat your hard disk.  Please be sure you specify the
correct filesystem size when using the mkfs command!  On some 3B systems,
most notable 3b15's, the system has no concept as to where the file
system physically ends on the disk (All fileystems "end" with the last
cylinder on the disk).  If you give it a size bigger than the filesystem should
be, it will go right ahead and scribble over the NEXT filesystem on the
disk.  "mkfs" is a command that should be used with great care; be careful.

john@polyof.poly.edu