Holy Harddisk space, Batman!

Discussion in 'Mac Basics and Help' started by eyeofnewt, Feb 12, 2007.

  1. eyeofnewt macrumors newbie

    Joined:
    Feb 12, 2007
    #1
    So today I get an alert from my OS that I'm running low on hard disk space. I check my Macintosh HD, and there's a staggeringly low number staring back at me. 16 GB. 16GB??! Yesterday I had at least 116GB of my original 250. What gives?!?!

    I haven't been downloading anything massive. I've just been doing a lot of video ripping and editing as of late. The only explanation I can think of is some malicious malware downloaded and unwittingly is taking over all the free disk space I had. I knew I should have been more cautious when google warned me about checking out that particular search result. I thought Macs weren't prone to internet illness.

    Just when I thought my days of computer related woes were behind me now that I've forsaken windows for Mac OS X....

    Could anyone help solve the mystery of the disappearing disk space? I don't know where to begin!
     
  2. WildCowboy Administrator/Editor

    WildCowboy

    Staff Member

    Joined:
    Jan 20, 2005
    #2
    This is usually the result of a runaway log file. Download WhatSize, OmniDiskSweeper or Disk Inventory X to help you look for large files. You're probably safe just deleting it once you track it down, as these events are usually just one-offs. But if it happens again, you'd want to start investigating what's causing it.
     
  3. eyeofnewt thread starter macrumors newbie

    Joined:
    Feb 12, 2007
    #3
    Thanks, WildCowboy. As it turns out, the most obvious solution is often the answer to problems like these.

    I followed the instructions laid out here <http://www.askdavetaylor.com/running_out_of_disk_space_on_a_mac.html> and discovered that the cause of my dissolving HD space was the newest .mov file I created. For some unfathomable reason, the 5 min mov I edited down from the original source avi I ripped saved as a 99GB file. Go figure!
     
  4. WildCowboy Administrator/Editor

    WildCowboy

    Staff Member

    Joined:
    Jan 20, 2005
    #4
    Ah yes...that's another common cause of it. Unfortunately, I don't know enough about video editing to really pinpoint what causes things like that. :eek:
     
  5. Counterfit macrumors G3

    Counterfit

    Joined:
    Aug 20, 2003
    Location:
    sitting on your shoulder
    #5
    No matter the reason, you shouldn't be getting that warning until you're under a few hundred MB.
     
  6. trainguy77 macrumors 68040

    Joined:
    Nov 13, 2003
    #6
    I got it when i was around 16 gb left. But now i bought a 320 gb drive. :D
     
  7. eyeofnewt thread starter macrumors newbie

    Joined:
    Feb 12, 2007
    #7
    Perhaps 16GB is the new preset number for the Intel Mac line?
     
  8. cobravap macrumors regular

    Joined:
    Oct 30, 2006
    #8
    it shouldnt be. I got to 7 gigs on my 160 gb hdd.
     
  9. Nermal Moderator

    Nermal

    Staff Member

    Joined:
    Dec 7, 2002
    Location:
    New Zealand
    #9
    Yeah I'm at 3.98 GB, and have been below 2, without that message popping up. I thought the trigger was at 500 MB.
     
  10. VoodooDaddy macrumors 65816

    Joined:
    May 14, 2003
    #10
    Thats crazy. I posted a similar thing a cpl weeks ago. I was just putting together a 5 seconds movie clip and for some unknown reason it turned into 32gb or something. I got a warning box saying my internal hdd was almost full but Id just checked it that morning and had 40gb free.

    Deleted file, back to normal.
     
  11. ElectricSheep macrumors 6502

    ElectricSheep

    Joined:
    Feb 18, 2004
    Location:
    Wilmington, DE
    #11
    Its very unwise to let your space get down to less than a gigabyte on 160/320/500 gig drives regardless of warnings given by the system. That's past the threshold beyond which HFS+ filesystem corruption occurs.
     
  12. mkrishnan Moderator emeritus

    mkrishnan

    Joined:
    Jan 9, 2004
    Location:
    Grand Rapids, MI, USA
    #12
    I wonder if the threshold that triggers the message is based on comparing the largest accessible contiguous space on the drive with the size of the swapfile.... when you've got an (inadvertently) 99GB movie file you're editing, you're probably using a lot more VM than you intend to be! ;)
     

Share This Page