Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!occrsh!occrsh.ATT.COM!gorgo.UUCP!authorplaceholder
From: authorplaceholder@gorgo.UUCP.UUCP
Newsgroups: comp.sys.att
Subject: Re: Disk Partitioning on 3b2's
Message-ID: <58300003@gorgo.UUCP>
Date: Sat, 4-Apr-87 17:29:00 EST
Article-I.D.: gorgo.58300003
Posted: Sat Apr  4 17:29:00 1987
Date-Received: Wed, 8-Apr-87 00:15:30 EST
References: <81@paisana.UUCP>
Lines: 19
Nf-ID: #R:paisana.UUCP:-8100:gorgo.UUCP:58300003:000:851
Nf-From: gorgo.UUCP!bsteve    Apr  4 16:29:00 1987


Chris Donahue writes:

>Read the "Hard Disk Partitioning" Section in the System Administrator's
>Guide (in Administrative Tasks major section) and look at the manual
>page for /etc/fmthard (in the SA Reference Manual). Also, take a
>look at the "sysadm partitioning" command. You'll get the idea.

I'll go one step further... The fmthard command is necessary since the 3B2 disk
partitioning is actually determined by vtoc stored on the disk. The fmthard
command writes a new vtoc onto the drive. This *always* cremes the data on
the drive, so take care. Note also that the filesystem boundaries need to
occur in correctly timed offsets on cylinder boundaries or performance will
suffer. "sysadm partitioning" knows about this necessity and will compensate
appropriately.

  Hope this helps,
   Steve Blasingame (Oklahoma City)
   bsteve@gorgo.att.com