From owner-freebsd-hackers  Sun Apr  2 21:49:29 1995
Return-Path: hackers-owner
Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id VAA21835 for hackers-outgoing; Sun, 2 Apr 1995 21:49:29 -0700
Received: from hq.icb.chel.su (icb-rich-gw.icb.chel.su [193.125.10.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id VAA21828 for <freebsd-hackers@freebsd.org>; Sun, 2 Apr 1995 21:49:13 -0700
Received: from localhost (babkin@localhost) by hq.icb.chel.su (8.6.5/8.6.5) id KAA03988; Mon, 3 Apr 1995 10:49:04 -0500
From: "Serge A. Babkin" <babkin@hq.icb.chel.su>
Message-Id: <199504031549.KAA03988@hq.icb.chel.su>
Subject: Re: large filesystems/multiple disks
To: terry@cs.weber.edu (Terry Lambert)
Date: Mon, 3 Apr 1995 10:49:04 -0500 (GMT-0500)
Cc: freebsd-hackers@FreeBSD.org
In-Reply-To: <9504010658.AA08921@cs.weber.edu> from "Terry Lambert" at Mar 31, 95 11:58:47 pm
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 902       
Sender: hackers-owner@FreeBSD.org
Precedence: bulk

> The main problem is that there needs to be file system support for the
> idea of additional disk space ...ie: one place where you can add
> things on.
> 
> This will work with IBM's JFS (obviously) or with a log structured
> file system, but precious little else.  UFS is particularly badly
> suited to doing this.  If you do what SPRITE does and shove all
> the inodes in one area and all of the data blocks in another, you
> can sort of do this for UFS.  The alternative is to preallocate
> a major large number of inodes in the first place (which is what I
> did) or to backup, remkfs the file system after adding the storage,
> and restore everything.

HP has UFS (they name it HFS) on LVM. I'm not shure but I think
that they use "cylinder group" as a quantum of space allocation.


		Serge Babkin

! (babkin@hq.icb.chel.su)
! Headquarter of Joint Stock Bank "Chelindbank"
! Chelyabinsk, Russia