Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!ames!sdcsvax!nosc!cod!hammond
From: hammond@cod.UUCP (John A. Hammond)
Newsgroups: comp.os.vms
Subject: Re: Diskquota vs. Directory /by_owner /grand /size
Message-ID: <777@cod.UUCP>
Date: Wed, 29-Jul-87 15:53:50 EDT
Article-I.D.: cod.777
Posted: Wed Jul 29 15:53:50 1987
Date-Received: Sat, 1-Aug-87 00:51:00 EDT
References: <870727-184908-1031@Xerox>
Organization: Naval Ocean Systems Center, San Diego
Lines: 14
Summary: Its a question of allocated vs used blocks


VMS uses a minimum allocation size cluster (default = 3) when
creating and extending files.  If a file has only 1 block
(512 bytes) in use then the directory size will show only 1
block in use even though the cluster_size is allocated.  This
can really byte (pun intended) if you have a user who creates
15000 1 block files on a disk that was set up with a cluster
size of 16 to handle large data files more efficiently.
Unfortunately the other 15 blocks allocated to each file were
totally unavailable to the user (unless he extended the
individual files which was not in his game plan) or anyone
else.  I got around the problem by moving the users files to 
a disk that had the default of 3 (still wasting a lot of 
space though).