Path: utzoo!mnetor!uunet!lll-winken!lll-lcc!ames!hao!gatech!purdue!i.cc.purdue.edu!j.cc.purdue.edu!pur-ee!iuvax!bsu-cs!cfchiesa From: cfchiesa@bsu-cs.UUCP (Sir Xetwnk) Newsgroups: comp.os.vms Subject: Re: lost disk space Message-ID: <2201@bsu-cs.UUCP> Date: 24 Feb 88 16:09:13 GMT References: <346@dalcsug.UUCP> Organization: CS Dept, Ball St U, Muncie, Indiana Lines: 52 Summary: Where your "Lost" space is! In article <346@dalcsug.UUCP>, logan@dalcsug.UUCP writes: > > [circumstances leading to disk-quota fill-up > > ... whenever I do a > SHOW QUOTA, I get a "blocks used" which is higher that the blocks used count > which I get with a dir/full. This is true even when blocks which are allocated > but not filled are taken into account (such as a one block file which is > allocated 3 blocks). > > Has anyone else run into this? How can I fix it? Yes, I run into this all the time, working for COmputing Services "help desk" user assistance dept... The standard answer is as follows. Because of the way VMS manages files, there is an "invisible" overhead of disk usage that doesn't show up when you do any form of DIR/SIZE, but which IS charged against your disk quota and therefore DOES show up when you do a SHOW QUOTA. This invisible overhead amounts to A MINIMUM of ONE BLOCK PER FILE AND PER DIRECTORY - and can easily be MORE than this. To find out where you REALLY stand, do the following. 1) Go to your main directory (SET DEFAULT SYS$LOGIN). 2) DIR/SIZE=ALL [...]*.*;* This will list all your directories and files, and will give you a final count of "# directories," "# files," and "blocks used." 3) ADD UP the "# directories," "# files," and "blocks used" (three quan- tities). 4) Compare THIS total against what SHOW QUOTA tells you - it should be MUCH closer. If not, THEN you have a problem -- write us again. In most cases, I never hear from the person again. In fact, many times, this method seems to say that the person is getting charged for FEWER blocks than SHOW QUOTA says, and the user keeps their mouth shut so as not to lose "a good thing!" Only in relatively rare cases does a user have a file stored in a directory they don't know about in another area. (Files are charged against the disk quota of the username CREATING the file, NOT that of the directory in which the file itself is placed!) Chris Chiesa, Senior, CS Dept., Ball State University, Muncie, IN -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><> Chris Chiesa <><><><><> <> {ihpn4|seismo}!{iuvax|pur-ee}!bsu-cs!cfchiesa <> <> cfchiesa@bsu-cs.UUCP <> <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>