RAxx disk partitons

Roy Smith roy at phri.UUCP
Fri Oct 17 07:29:15 AEST 1986


In article <4539 at brl-smoke.ARPA> conley%ukans.csnet (Dennis R. Conley)
wonders about the default 4.2BSD RA-xx partition sizes.

	I never did figure out exactly why the default partition sizes are
as they are.  One of the problems is that it is not easy for the software
to tell if you actually have an RA60, 80, or 81 out there so they make the
start of the last partition high enough to fit on the smallest disk (the
ra80, but it beats me why anybody would buy an ra80 instead of an ra81) and
they let the end float to fill the disk.  On a ra81, that leaves a bunch of
rather small partitions, and one huge one.

	Another problem, I think, is that I've seen DEC literature which
alternately lists the RA81 as having 51 or 52 sectors per track (I believe
51 is the right number, but don't hold me to that).  The UDA-50 does a
pretty good job of hiding cylinder boundaries anyway.

	At any rate, one of the first things I did when I set up 4.2 was to
redefine the partition table in the uda driver.  The comments below explain
my motivation; I hope it makes sense.  In practice, we have /usr on ra0d,
use f and h for user's files, and have /tmp on e.  If we ever got a second
ra81 (not likely, I'd rather buy more eagles for my Suns), I suppose we'd
use ra[123][gh] for additional user space.

Filesystem    kbytes    used   avail capacity  Mounted on
/dev/ra0a       7429    3931    2755    59%    /
/dev/ra0e       7429      53    6633     1%    
/dev/ra0d      96547   79117    7775    91%    
/dev/ra0f      96547   85492    1400    98%    
/dev/ra0h     201054  176378    4570    97%    


 */
 *	Roy Smith, PHRI, 28-May-84
 *	Changed partition table.  The table is hard-wired for a RA-81.
 *	The driving force in the layout was to provide several large
 *	partitions of the same size so that file systems could be
 *	moved around in an emergency.  Partitions 'a' and 'e' are both
 *	the same size and are meant for a root and a backup root.
 *	Partition 'h' is the big one and is for the user's files.
 *	Partition 'd' will hold the /usr file system with all the
 *	optional stuff (ingres, vfont, etc.) and still have plenty
 *	of room for expansion.  Partition 'f' is the same size as 'd'
 *	and is intended for disk-to-disk midnight incremental file
 *	system dumps or for an additional file system.  Partition 'g'
 *	is the concatenation of 'd', 'e', and 'f' and is exactly the
 *	same size as 'h'.  Partition 'b' is for swap. The 4 commonly
 *	used partitions ('a', 'b', 'h', and 'd') are near each other.
 *	Using the backup root on 'e' instead of the standard one on
 *	'a' still leaves you with 4 adjacent file systems.  Of course,
 *	partition 'c' maps the whole disk.
 */

/* THIS SHOULD BE READ OFF THE PACK, PER DRIVE */
struct size {
	daddr_t	nblocks;
	daddr_t	blkoff;
} ra_sizes[8] =
{
	16422,     0,		/* A = cyl 0 - 22	*/
	30702,     16422,	/* B = cyl 23 - 65	*/
	891072,    0,		/* C = cyl 0 - 1247	*/
	202776,    469098,	/* D = cyl 657 - 940	*/
	16422,     671874,	/* E = cyl 941 - 963	*/
	202776,    688296,	/* F = cyl 964 - 1247	*/
	421974,    469098,	/* G = cyl 657 - 1247	*/
	421974,    47124	/* H = cyl 66 - 656	*/
};
/* END OF STUFF WHICH SHOULD BE READ IN PER DISK */
-- 
Roy Smith, {allegra,philabs}!phri!roy
System Administrator, Public Health Research Institute
455 First Avenue, New York, NY 10016



More information about the Comp.unix.wizards mailing list