System Thinks HD is Full
in [Mac Systems]
|
Prev: Mac tablet
Next: System Thinks HD is Full -- Fixed
From: Tom Stiller on 7 Nov 2009 13:25 In article <071120091130035772%star(a)sky.net>, Davoud <star(a)sky.net> wrote: > MB Pro 17, 10.6.1, 4 GB RAM... > > I installed a 500 GB drive in this machine some months ago. It has > performed flawlessly. It has (or had until last night) about 206 GB of > free space. > > In the wee hours of this morning, as I was working on an image in > Photoshop, a pop-up warning told me that the disk was full. I was > running quite a few apps besides Photoshop; for example, I was running > Screen Sharing to control another MB Pro that was collecting image data > in my little astronomical observatory > http://www.primordial-light.com/macastronomer.html>. > > I have done the simple things: Ran fsck. Booted from my SuperDuper! > backup FW drive and run Disk Utility's repair and repair permissions. > Erased free space. Rebuilt the directory with Disk Warrior. Checked > files and folders with Disk Warrior. > > The drive now shows 4.3 GB available, which means that a bit over 200 > GB is missing. > > I have a full SuperDuper! backup and a Time Machine backup of my home > directory, plus a backup to a terabyte RAID drive, so I am not much > concerned about losing data, but the time involved in restoring from > SuperDuper is considerable, so if anyone has a fix short of a full > restore I would be grateful to hear of it! > I had that happen once when a runaway process was creating files as fast as it could, although I had no clue about the cause at the time. I located the problem by running the "Check all Files & Folders" option of the "Files" pane of DiskWarrior. The scan show there were more files in a particular directory the allowed; that provided the necessary clue. -- Tom Stiller PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF
From: Jim Gibson on 9 Nov 2009 13:43 In article <vilain-484F7A.12472307112009(a)individual.net>, Michael Vilain <vilain(a)NOspamcop.net> wrote: > Most MacOS X systems do a good job of splitting the system/root stuff > from the user stuff. If you have some weird application that runs as > root and doesn't clean up it's log files, you can run > > sudo du -sh /* > > It will take quite a while to run and show you the system directories. > You may want to stop it when it hits the /Volumes directory if you have > multiple volumes. You can add the -x option to the du utility to prevent it from reporting on volumes other than your startup disk: sudo du -xsh /* See 'man du' for details. -- Jim Gibson
From: thepixelfreak on 9 Nov 2009 14:10 On 2009-11-07 08:30:03 -0800, Davoud <star(a)sky.net> said: > MB Pro 17, 10.6.1, 4 GB RAM... > > I installed a 500 GB drive in this machine some months ago. It has > performed flawlessly. It has (or had until last night) about 206 GB of > free space. > > In the wee hours of this morning, as I was working on an image in > Photoshop, a pop-up warning told me that the disk was full. I was > running quite a few apps besides Photoshop; for example, I was running > Screen Sharing to control another MB Pro that was collecting image data > in my little astronomical observatory > http://www.primordial-light.com/macastronomer.html>. Nope, no suggestions from me. I now have serious telescope envy. And that Astrophysics mount sent me over the edge. If you're running 10.6.x Grand Perspective is very useful. If 10.5.x then Disk Inventory X is the analog to the former. -- thepixelfreak
From: Fred Moore on 9 Nov 2009 17:47 In article <071120091309372612%star(a)sky.net>, Davoud <star(a)sky.net> wrote: > Davoud: > > > The drive now shows 4.3 GB available, which means that a bit over 200 > > > GB is missing. > > Fred Moore: > > If it were my machine, I'd use OnyX (free/donationware) or equivalent to > > turn on Show Invisibles. Then I'd display the root directory and sort by > > size, descending order. Any folder/directory over 100GB would be > > suspect. Open it/them up and see what's so large. My guess is that there > > is either a runaway log file or a scratch file which isn't being > > properly deleted. The directory, /private/, and its sub-directories, > > /private/tmp/ and /private/var/, are likely candidates; but the > > culprit(s) could easily be somethng else. (There are terminal commands > > to do this, but I don't know what they are.) > > ls -l -a is one way. Quicker than practically any download! Always > happy to help the helper. So Davoud, now that you, Michael Vilain, and Jim Gibson have provided terminal commands (thanks to all of you), have you made any progress in identifying a culprit? (And, NICE star hardware!)
From: Fred Moore on 9 Nov 2009 17:59
In article <fmoore-9CB84B.17473309112009(a)feeder.eternal-september.org>, Fred Moore <fmoore(a)gcfn.org> wrote: > In article <071120091309372612%star(a)sky.net>, Davoud <star(a)sky.net> > wrote: > > Davoud: > > > > The drive now shows 4.3 GB available, which means that a bit over 200 > > > > GB is missing. > > > > Fred Moore: > > > If it were my machine, I'd use OnyX (free/donationware) or equivalent to > > > turn on Show Invisibles. Then I'd display the root directory and sort by > > > size, descending order. Any folder/directory over 100GB would be > > > suspect. Open it/them up and see what's so large. My guess is that there > > > is either a runaway log file or a scratch file which isn't being > > > properly deleted. The directory, /private/, and its sub-directories, > > > /private/tmp/ and /private/var/, are likely candidates; but the > > > culprit(s) could easily be somethng else. (There are terminal commands > > > to do this, but I don't know what they are.) > > > > ls -l -a is one way. Quicker than practically any download! Always > > happy to help the helper. > > So Davoud, now that you, Michael Vilain, and Jim Gibson have provided > terminal commands (thanks to all of you), have you made any progress in > identifying a culprit? Nevermind. I didn't see that you had posted a separate thread with the results. Thanks for letting us know. |