Path: utzoo!utgpu!cunews!bnrgate!brchh104!brchs1!bnr.ca!rice.edu!sun-spots-request From: phil@cgrg.ohio-state.edu Newsgroups: comp.sys.sun Subject: NO SOLUTION YET Re: Where oh where has my disk space gone? Keywords: Miscellaneous Message-ID: <2774@brchh104.bnr.ca> Date: 9 May 91 23:05:00 GMT Sender: news@brchh104.bnr.ca Organization: Sun-Spots Lines: 51 Approved: Sun-Spots@rice.edu X-Original-Date: 29 Apr 91 19:23:07 GMT X-Refs: Original: v10n91 X-Sun-Spots-Digest: Volume 10, Issue 99, message 12 X-Note: Submissions: sun-spots@rice.edu, Admin: sun-spots-request@rice.edu I have gotten several replies to my query as to where over 10 Mbytes of disk space have disappeared to. Most related to a process creating a file, rm the file, but the process still fills the area. Others related to similar 'hidden' files. One wondered if I tried it as root? Hmmmm . . . of course . . . Anyway, I brought down the system, brought up the miniroot off of tape and fsck'ed the partition . . . I did find @4 Mbytes this way. Under the miniroot, the root partition, I mounted the root partition of this disk as /a and the /usr partition as /d (so I could use du). From df: Filesystem kbytes used avail capacity Mounted on /dev/xy0a 30191 21692 5479 80% /a /dev/xy0d 132904 115730 3883 97% /d BUT, when I did a du on these 2 partitions, I get a WILDLY different answer (from the last line): 13201 /a 115730 /d Hmmmm . . . the /d 'du' matches the 'df' estimation, but the /a 'du' is still almost 8 Mbytes off!!!!! Now, mind you this was NOT on a working disk, I had installed the miniroot and was mounting these partitions (I was NOT using the root partition off of the disk). I thought I might have screwed up the partitioning (I DIDN'T reformat when I just moved up from 4.0 to 4.1.1, just had suninstall do it's newfs thing), but wouldn't a screwed up partition shown up in 4.0???: Current partition table (original xy0): partition a - starting cyl 0, # blocks 64320 (64/0/0) partition b - starting cyl 64, # blocks 196980 (196/0/0) partition c - starting cyl 0, # blocks 1743675 (1735/0/0) partition d - starting cyl 260, # blocks 283410 (282/0/0) partition e - starting cyl 542, # blocks 37185 (37/0/0) partition f - starting cyl 579, # blocks 423105 (421/0/0) partition g - starting cyl 1000, # blocks 510540 (508/0/0) partition h - starting cyl 1508, # blocks 228135 (227/0/0) I'm baffled . . . Any help? I never had this problem with OS 4.0, just since I upgraded to OS 4.1.1 . . . Thanks . . . Phil Ritzenthaler The Advanced Computing Center for the Arts & Design (ACCAD) Systems Manager The Ohio State University UUCP: ...!{pyramid,killer}!grumpy.cgrg.ohio-state.edu!phil (614) 292-3416 ARPA: phil@grumpy.cgrg.ohio-state.edu