Why do I get startup disk full error even though I have 2 gb free?

My startup disk is getting full (I get error message) after 1 day of usage.
In the finder, after a restart, it says I have 2.05 GB available.
Then after working for a while (yes, I keep a few apps open - usually Entourage, Word, Firefox, iTunes -- but c'mon, I have 1 GB of RAM) I get an error that my startup disk is full.
This is my Terminal Log after getting the error:
Processes: 68 total, 2 running, 66 sleeping... 241 threads 16:52:11
Load Avg: 0.92, 0.79, 0.71 CPU usage: 40.4% user, 8.4% sys, 51.1% idle
SharedLibs: num = 204, resident = 38.2M code, 5.36M data, 10.5M LinkEdit
MemRegions: num = 11633, resident = 436M + 11.8M private, 161M shared
PhysMem: 237M wired, 448M active, 268M inactive, 954M used, 69.9M free
VM: 11.3G + 138M 409448(1) pageins, 267438(0) pageouts
This is my Terminal Log after startup:
Processes: 59 total, 2 running, 57 sleeping... 165 threads 17:00:14
Load Avg: 0.31, 0.11, 0.04 CPU usage: 0.0% user, 2.8% sys, 97.2% idle
SharedLibs: num = 143, resident = 25.7M code, 4.27M data, 7.07M LinkEdit
MemRegions: num = 4731, resident = 56.3M + 13.4M private, 81.0M shared
PhysMem: 174M wired, 110M active, 139M inactive, 424M used, 599M free
VM: 6.67G + 104M 21081(0) pageins, 0(0) pageouts
Any suggestions?

That isn't much hard drive space open. I have heard 10% should be free, so if you have an 80 GB drive you need 8 GB free; if you have 100, 10 free and so on. Even if the figure is 5% you are still too low.
Your error message said you had 267438 pageouts to the disk which seems huge. That means your physical RAM can't keep up and is sending out data to the hard disk which is virtual memory, not real RAM memory. I don't know enough about it to say for sure but that seems like a recipe for this kind of trouble.

Similar Messages

I keep getting "startup disk full" message even when I already moved all my files/documents to an external hard disk

Dear all,
What should I do? I keep getting the "startup disk full" message even when I already moved all my files and documents to an external hard disk.
Thanks a heap.

For information about the Other category in the Storage display, see this support article.
Empty the Trash if you haven't already done so. If you use iPhoto, empty its internal Trash first:
iPhoto ▹ Empty Trash
Do the same in other applications, such as Aperture, that have an internal Trash feature. Then reboot. That will temporarily free up some space.
According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation. You also need enough space left over to allow for growth of your data. There is little or no performance advantage to having more available space than the minimum Apple recommends. Available storage space that you'll never use is wasted space.
If you're using Time Machine to back up a portable Mac, some of the free space will be used to make local snapshots, which are backup copies of files you've recently deleted. The space occupied by local snapshots is reported as available by the Finder, and should be considered as such. In the Storage display of System Information, local snapshots are shown as Backups. The snapshots are automatically deleted when they expire or when free space falls below a certain level. You ordinarily don't need to, and should not, delete local snapshots yourself.
See this support article for some simple ways to free up storage space.
You can more effectively use a tool such as OmniDiskSweeper (ODS) to explore your volume and find out what's taking up the space. You can also delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one.
Deleting files inside an iPhoto or Aperture library will corrupt the library. Any changes to a photo library must be made from within the application that created it. The same goes for Mail files.
Proceed further only if the problem isn't solved by the above steps.
ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
Back up all data now.
If you have more than one user account, make sure you're logged in as an administrator. The administrator account is the one that was created automatically when you first set up the computer.
Install ODS in the Applications folder as usual. Quit it if it's running.
Triple-click anywhere in the line of text below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C:
sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
Launch the built-in Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning to be careful. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The application window will open, eventually showing all files in all folders, sorted by size with the largest at the top. It may take a few minutes for ODS to finish scanning your files.
I don't recommend that you make a habit of doing this. Don't delete anything while running ODS as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means. When in doubt, leave it alone or ask for guidance.
When you're done with ODS, quit it and also quit Terminal.

Why am I getting a "Disk Full" error message when attempting to export?

I am trying to export my movie at large quality or higher and every time it gives me a "disk full" error. However, I was able to successfully export it at medium quality. I don't understand why I would be getting that error though because both my internal hard drive and external drive, which I am exporting from (but onto the internal), have ample amount of space to accommodate for a large or HD quality video. Any help would be much appreciated!

How much space do you have?

Startup Disk Full Error - Please help

Dear ALL,
I have started to notice recently that when I run Photoshop CS on my Mac OSX Tiger, I am getting the Startup Disk Full error message.
I have no clue as to how to correctly fix this issue. I looked at my HD and I seem to have 32GB available, which I would have thought would have been ample space. I have started to remove unwanted files and backup to CD large image files. So this should free up some more space. The question is will this be enough to get rid of this issue and is it associated with the amount of HD space on my drive? or would I need to run some script etc? or download/buy some other product to fix this?
Your help is greatly appreciated.
Max

OK I tried Macaroni...and when I tried to work with a TIFF file I get the same Startup Disk is FULL message. The I get an adobe message saying Scratch Disk is FULL.
Any further suggestions would be appreciated.

What do i need to do when i get a startup disk full error?

What do i need to do when i get a startup disk full error? I can't update software or use my MacAir at all.

Empty the Trash if you haven't already done so. If you use iPhoto, empty its internal Trash first:
iPhoto ▹ Empty Trash
Then reboot. That will temporarily free up some space.
According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation. You also need enough space left over to allow for growth of your data. There is little or no performance advantage to having more available space than the minimum Apple recommends. Available storage space that you'll never use is wasted space.
If you're using Time Machine to back up a portable Mac, some of the free space will be used to make local snapshots, which are backup copies of files you've recently deleted. The space occupied by local snapshots is reported as available by the Finder, and should be considered as such. In the Storage display of System Information, local snapshots are shown as "Backups." The snapshots are automatically deleted when they expire or when free space falls below a certain level. You ordinarily don't need to, and should not, delete local snapshots yourself.
To locate large files, you can use Spotlight. That method may not find large folders that contain a lot of small files.
You can more effectively use a tool such as OmniDiskSweeper (ODS) to explore your volume and find out what's taking up the space. You can also delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one.
Deleting files inside an iPhoto or Aperture library will corrupt the library. Any changes to a photo library must be made from within the application that created it. The same goes for Mail files.
Proceed further only if the problem isn't solved by the above steps.
ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
Back up all data now.
Install ODS in the Applications folder as usual. Quit it if it's running.
Triple-click anywhere in the line of text below on this page to select it, then copy the selected text to the Clipboard by pressing the key combination command-C:sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The application window will open, eventually showing all files in all folders. It may take some minutes for ODS to list all the files.
I don't recommend that you make a habit of doing this. Don't delete anything while running ODS as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means. When in doubt, leave it alone or ask for guidance.
When you're done with ODS, quit it and also quit Terminal.

Why do I get a start-up disk full error message? I have 800 GB and have used approx. 249.

why do I get a start-up disk full error message? I have 800 GB and have used approx. 249.

Here's the appropriate answer:
Last login: Fri May 23 13:19:44 on console
[la-mes883094mn:~] joannhackett% diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *251.0 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         250.0 GB   disk0s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *249.7 GB   disk1
[la-mes883094mn:~] joannhackett% diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 098533C8-3936-4FB1-BCB8-2FE94E6E0500
    =========================================================
    Name:         Macintosh HD
    Status:       Online
    Size:         250006216704 B (250.0 GB)
    Free Space:   16777216 B (16.8 MB)
    |
    +-< Physical Volume 9518DA81-D7D6-4D76-8B4D-1F235D8AEA3A
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk0s2
    |   Status:   Online
    |   Size:     250006216704 B (250.0 GB)
    |
    +-> Logical Volume Family C1A37CDE-6624-4094-A29A-2BB706380979
        Encryption Status:       Unlocked
        Encryption Type:         AES-XTS
        Conversion Status:       Complete
        Conversion Direction:    -none-
        Has Encrypted Extents:   Yes
        Fully Secure:            Yes
        Passphrase Required:     Yes
        |
        +-> Logical Volume 7175D310-4566-455D-9C50-1BD4CCF257CE
            Disk:                  disk1
            Status:                Online
            Size (Total):          249670668288 B (249.7 GB)
            Conversion Progress:   -none-
            Revertible:            Yes (unlock and decryption required)
            LV Name:               Macintosh HD
            Volume Name:           Macintosh HD
            Content Hint:          Apple_HFS
[la-mes883094mn:~] joannhackett% mount
/dev/disk1 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
map -fstab on /Network/Servers (autofs, automounted, nobrowse)
localhost:/4OM-aHuM-mGML9PliXARLB on /Volumes/MobileBackups (mtmfs, nosuid, read-only, nobrowse)
[la-mes883094mn:~] joannhackett% df -m /
Filesystem 1M-blocks   Used Available Capacity iused   ifree %iused Mounted on
/dev/disk1    238104 227599     10255    96% 58329357 2625394   96%   /
[la-mes883094mn:~] joannhackett%
As for the 251 disk, what is this? I assume it's the wrong kind of memory? Thanks, Jo Ann

I've cleared almost 30 gig off of my hard drive in the past 2 weeks, and it will temporarily show that in the Get Info box. But hours later, I am still getting a disk full error and all of the memory has disappeared.

I've cleared almost 30 gig off of my hard drive in the past 2 weeks, and it will temporarily show that in the Get Info box. But hours later, I am still getting a disk full error and all of the memory has disappeared. I have cleared my backup logs from Time Machine, checked the mail folder, cleaned out tons of photos and videos and it still keeps filling back up.
In checking the log files, here is the message repeated over and over....
Jul 4 07:18:13 Donald-Keele-Jrs-iMac-123.local CalendarAgent[213]: CoreData: error: (21) I/O error for database at /Users/donjr/Library/Calendars/Calendar Cache. SQLite error code:21, 'unable to open database file'
Jul 4 07:18:13 Donald-Keele-Jrs-iMac-123.local CalendarAgent[213]: Core Data: annotation: -executeRequest: encountered exception = I/O error for database at /Users/donjr/Library/Calendars/Calendar Cache. SQLite error code:21, 'unable to open database file' with userInfo = {
NSFilePath = "/Users/donjr/Library/Calendars/Calendar Cache";
NSSQLiteErrorDomain = 21;
Jul 4 07:18:14 Donald-Keele-Jrs-iMac-123.local cfprefsd[180]: CFPreferences: error creating file /Users/donjr/Library/Preferences/com.apple.iPhoto.plist.t3l894p: 28
Jul 4 07:18:30 Donald-Keele-Jrs-iMac-123.local Printer Pro Desktop[275]: Empty task
Jul 4 07:18:33 Donald-Keele-Jrs-iMac-123.local Microsoft Sync Services[8149]: [0x16697c0] |ISyncSession|Warning| com.microsoft.Entourage2008: transitioning to cancel - session cancelled by server: Client 'com.microsoft.Entourage2008' tried to start a session for the plan 45AD80C3-0D52-4CF2-8CBA-103564B6C47C and the plan no longer exists.
Jul 4 07:18:33 Donald-Keele-Jrs-iMac-123.local Microsoft Sync Services[8149]: Warning: NSBundle NSBundle </Applications/Microsoft Office 2008/Office/Microsoft Sync Services.app/Contents/Resources/MicrosoftOfficeNotes.syncschema> (not yet loaded) was released too many times. For compatibility, it will not be deallocated, but this may change in the future. Set a breakpoint on __NSBundleOverreleased() to debug
Jul 4 07:18:33 Donald-Keele-Jrs-iMac-123.local Microsoft Sync Services[8149]: Warning: NSBundle NSBundle </Users/donjr/Library/Sync Services/Schemas/MicrosoftOfficeNotes.syncschema> (not yet loaded) was released too many times. For compatibility, it will not be deallocated, but this may change in the future. Set a breakpoint on __NSBundleOverreleased() to debug
Jul 4 07:18:45 Donald-Keele-Jrs-iMac-123 kernel[0]: (default pager): [KERNEL]: default_pager_backing_store_monitor - send LO_WAT_ALERT
Jul 4 07:18:45 Donald-Keele-Jrs-iMac-123 kernel[0]: macx_swapoff SUCCESS
Jul 4 07:19:31 Donald-Keele-Jrs-iMac-123.local Printer Pro Desktop[275]: Empty task
Any ideas on what to do next?
I'm running and iMac 20-inch early 2009
Processor 2.66 GHz Intel Core 2 Duo
Memory 8 GB 1067 MHz DDR3
Graphics NVIDIA GeForce 9400 256 MB
Software OS X 10.8.4 (12E55)

Step 1
Quit Calendar. Triple-click the line below to select it:
~/Library/Calendars/Calendar Cache
Right-click or control-click the highlighted line and select
Services ▹ Reveal
from the contextual menu. A Finder window should open with a file named "Calendar Cache" selected.
Move the selected file to the Trash. There may be one or two other files in the same folder with names that begin in "Calendar Cache". If so, delete those files too.
Step 2
Empty the Trash if you haven't already done so. If you use iPhoto, empty its internal Trash as well:
iPhoto ▹ Empty Trash
Then reboot. That will temporarily free up some space.
According to Apple documentation, you need at least 9 GB of available space on the startup volume (as shown in the Finder Info window) for normal operation. You also need enough space left over to allow for growth of your data. There is little or no performance advantage to having more available space than the minimum Apple recommends. Available storage space that you'll never use is wasted space.
To locate large files, you can use Spotlight. That method may not find large folders that contain a lot of small files.
You can more effectively use a tool such as OmniDiskSweeper (ODS) to explore your volume and find out what's taking up the space. You can also delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one.
Deleting files inside an iPhoto or Aperture library will corrupt the library. Any changes to a photo library must be made from within the application that created it. The same goes for Mail files.
Proceed further only if the problem isn't solved by the above steps.
ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
Back up all data now.
Install ODS in the Applications folder as usual. Quit it if it's running.
Triple-click the line of text below to select it, then copy the selected text to the Clipboard (command-C):
sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The application window will open, eventually showing all files in all folders. It may take some minutes for ODS to list all the files.
I don't recommend that you make a habit of doing this. Don't delete anything while running ODS as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means. When in doubt, leave it alone or ask for guidance.
When you're done with ODS, quit it and also quit Terminal.

Adobe Photoshop Scratch Disk Full/Startup Disk Full error - PLEASE HELP

Dear ALL,
I have started to notice recently that when I run Photoshop CS on my Mac OSX Tiger, I am getting the Startup Disk Full error message. Never happended before.
Since my initial post I downloaded Macaroni (utility) and have run the daily/weekly/monthly backups, checked the /private/var/vm and /private/var/log and /Volumes. Nothing unusual there...
When I started getting this error I had 32GB left on a looked at my HD and I seem to have 32GB available on a 152GB drive. Now after deleting I have 76GB capacity left.
But when I tried to open a Photoshop PSD or TIFF file and do a crop I still get tge Startup Disk is Full error followed by the Adobe Photoshop error Scratch Disk is Full.
I am thinking of running the Disk Utility from the Applications/Utilities/Disk Utility and doing a Verify Disk and Verify Disk Permissions followed by Repair Disk Permissions. I will be logged into the machine whilst doing this. Is there any danger in this as I have read elsewhere that I need to do this from a bootable volume. If that is the case how do I create a bootable disk/cd? If not then what is the cure to my Disk Full as surely there is now nearly 50% FREE!!!!!
Please help.
Max

PS will always use the boot disk for scratch to some extent even with an alternate primary scratch disk.
Be sure to turn off Spotlight as it causes problems.
4GB of RAM would be nice, I understand small files don't work well if there is more than 4GB RAM but large files will. OS X uses free RAM as cache and RAM disk before using disk drives.
How much RAM is allocated to PS? More RAM would help.
A dedicated lean boot drive helps. Install just what is needed for your work, use a separate drive for data, and yet another RAID volume for scratch.
When in doubt, backup with SuperDuper, and do an erase and then restore. Always backup before repairing; and never, ever, use an old version of Tiger CD/DVD - like 10.4.2 on 10.4.7/.8. Use "fsck" instead, or your emergency boot drive.
Also, give Applejack a shot and delete the cache folders and swap files from time to time to keep a system humming. CS/CS2 and Tiger benefit nicely from more RAM.

Shutdown while startup, disk full error on verbose

i have a mac book pro when starting , the gray screen appears, later the apple and 10 seconds later aprox, turn off
i try verbose mode and after turn off i can see a message “Disk full error"
Operating system: OSX 10.9
322MB FREE OF 300GB .. (my girlfriend is a graphic designer and does not pay any attention to alerts ..)
I prove, smc reset, 2 chime sound test, safe mode (turn off too).
performing tests were:
1. Launch the recovery console ( from bootable usb osx mavericks) ,
a. i probe unmount the volume Macintosh HD, not possible, because, its in use.
a. verify disk ( Macintosh HD) , "the disk needs to be repair"
b . repair disk ( Macintosh HD) , Keys out of order , ... Utility cant repair disk , and restore your backed -up files
c . Check disk (320gb toshiba ..) , the partition map need to be repaired , because ... Problem with the EFI system partitions
d . repair disk (320gb toshiba ..) , but ... when repair , try with Recovery HD, and works fine (not Macintosh HD)
After that, the disc automatically unmounts and its not possible mount again (from terminal said "mount: /dev/disk0s2: unknow special file of file system")
2 . Probe I start with a recovery console (local disk)
same results (on repair 320gb toshiba.. the first time i run it, said "can’t perform live”, after that, same result like point 1
3. restart, with recovery console (local disk)
a. launch terminal and try to delete manually , go to /dev/disk0s2 (/Volumes/Macintosh HD) and can browse the disk (ex /Users/xxxx/Desktop), but when tried rm, appears “Read-Only File System"
4. Remove the HD from mac and put it on case, when i connect it via USB to another mac book pro, the OS, saids “can’t recognize the disk, initialize, ignore, eject)
it is possible unmount the volume and remount like read-write from recovery console?
is it possible to access the data in read-write mode for any way to delete some huge files?
its the only solution mount and external disk and make and tedious scp from Terminal???, if its possible
regards, sorry for my bad English
Dario

There are lots of hidden directories. There could be actual data instead of alias mount points under "/Volumes" which is often one reason.
There are a couple programs to show where space is going, as well as sort output from terminal, but I prefer OmniGroup OmniDiskSweeper - look on MacUpdate - to show and access files. Program works fine even though shareware.
And yes, you might want to use the Raptor? for something else and get even WD 640GB for $75, or the 3rd gen VelociRaptor 300GB $289.
There are threads in "Using Leopard" regularly about "where did my space go."

I have an iphone 3GS and suddenly am getting a "storage almost full message" even though I have 1.4 GB of free space. Now I cannot text. How do I trouble shoot this?

I have an iphone 3GS and suddenly am getting a "storage almost full message" even though I have 1.4 GB of free space. Now I cannot text. How do I trouble shoot this? I recently upgraded to version 6.1.3 if that helps.

When you sync using iTunes on your computer, do you see a lot of "Other" at the bottom of the iTunes Summary Page for your iPhone? If you do, try a "Restore iPhone ...". That should help.
Hopefully that would do it for you. If not, the next (more drastic) step would be to restore again as above, but choose "Restore as New" and then manually sync. Omit any apps that might be suspcious in their space use (primarily Game Center apps).

Hi...i cannot connect to my imessage it always show a message says network error even though i have a network..please help..tnx..

Hi...i cannot connect to my imessage it always show a message says network error even though i have a network..please help..tnx..
[email protected]

Both parties must be connected to wifi to use FaceTime (and you must have FaceTime turned on in Settings>Facetime). If you're phone shows 3G at the top when it's on, you're not connect to wifi; you'll have to solve that problem first.

Startup disk full error - boots normally but won't start finder

I'm having a problem in which my iMac when it boots gives me an error that the startup disk is full, but other than that it can boot normally and allow me to log in, but after that the startup stalls. I never get past the default "outer space" desktop image and finder never starts, so there's no icons, no dock, and nothing on the menu bar. What's weird is that Safari and Mail start and I can see them because I believe I have them starting automatically at boot. Safari works (I'm using it now to enter this discussion). Mail on the other hand starts but is hung checking for the servers for incoming mail.
I've tried to boot in safe mode (holding down Shift key at startup), but it doesn't work.
I've tried to boot in single user mode (holding down cmd-S at startup), but it doesn't work either.
I've tried to boot from Snow Leopard installation media (holding down C at startup), but it doesn't work as well.
Each time I try one of these alternate boot methods, it just takes me to the normal login screen with the startup disk full message. I click OK, login, and get stuck.
I'm just trying to get the finder started so that I can delete some files, but I just can't get that far. It's strange that the browser works perfectly and internet connection is fine, but nothing else works.
Thoughts? Thanks. - Mike

Hi Lina, and welcome to Apple Discussions.
Safe Mode might allow you to boot and free up some space.
If you have access to another Mac and a FireWire cable, another option would be to use FireWire Target Disk Mode to transfer data to the other Mac and delete it on your MBA.
If either way works, you want to open up somewhere around 15% free space. Once you do that, run Repair Disk: Boot from install disc (insert disc>restart>immediately hold down c key and keep holding it until you see “Preparing Installation”)>at first screen select the language and click Continue> click on the Utilities Menu in the menu bar>open Disk Utility>select your HD in the panel on the left side>click Repair Disk at bottom of main window. Run this at least twice, and keep running it until it says “appears ok” twice in a row. If that doesn’t happen, you may need a stronger utility such as DiskWarrior or if the directory is damaged beyond repair, you may need to reinstall the OS, or you may have a damaged HD (repair utilities can only repair the directory structure, not the HD itself).
Ultimately, though, it sounds like you need a larger HD . . . .

Startup Disk Full Error when it is not full.

When ever my swap files reach the size of the free space on my startup disk (60GB) I receive this error even though my swap files are stored on a separate disk with 500GB free. The startup disk continues to have 60GB free when this error occurs. The swap file disk has 440GB free. I know the program has a memory leak, but it should continue to run until the swap file disk is full. Please help!

If you open System Preferences and then go to the Software Update pane, you can click on the Installed Updates tab to see when various updates were installed. Look in particular for the Mac OS X Update Combined 10.5.2 and the Leopard Graphics Update; when were they installed relative to 2/23.
Three things you can do as general trouble-shooting steps, if you haven't done them already.
Run Disk Utility. Use the Repair Disk Permissions routine under First Aid tab on your internal drive.
Restart from the Mac OS X installation disk. From the Installer's Utilities menu, select Disk Utility. Use the Repair Disk routine under First Aid on your internal drive. See if that reports any problem.
Reset PRAM. Some display parameters are stored in PRAM, so this may help.
http://docs.info.apple.com/article.html?artnum=2238

Why do i constantly get 1009 and 100 errors even though i'm updating what i previously downloaded from same country and from the same app store??...its just simply awful

It has been like a month since i can't update my apps which i downloaded from the App Store...now i keep getting error1009 followed by error100 even though i'm still living in the same country and using the same account and updating from the same App Store...this is getting awful,painful and very frustrating???is there any solution...even if when i try to download from third parties,i just get sent back to the same awful App Store...So WHAT is the Solution??????????

I would delete the apps that you are trying to update. The MAS should then offer to install the app and it will install the updated version.
If you are afraid of completely loosing the app then either copy the app to an ext HDD or put it in the Trash, but do not empty the Trash until you are sure that the MAS has installed a new version.

Getting an VISANS timeout error even though VISA Status is 0

I have an application that runs well on my development system but consistently fails at the user site giving out timeout errors even though the user experiences no time outs. Indeed, VISA returns a success status. Yet, it raises timeout exceptions such as in this segment from my trace log:
DefaultSource, Verbose, 8, Setting timeout to 30000, "CONNECT", 2008-08-12 00:47:21Z, 2077539389311920
DefaultSource, Information, 0, GPIB0::26::INSTR termination character set to 10, "CONNECT", 2008-08-12 00:47:21Z, 2077539630487436
DefaultSource, Verbose, 8, Checking GPIB0::26::INSTR message available, "FR, CONNECT", 2008-08-12 00:47:21Z, 2077539636730532
DefaultSource, Verbose, 8, Flushing read GPIB0::26::INSTR buffer, "FR, CONNECT", 2008-08-12 00:47:21Z, 2077539673800216
DefaultSource, Error, 2, Flushing read GPIB0::26::INSTR buffer failed: NationalInstruments.VisaNS.VisaException: Timeout expired before operation completed. VISA error code -1073807339 (0xBFFF0015), ErrorTimeout
   at NationalInstruments.VisaNS.Internal.ErrorChecker.CheckStatusAndThrow(Int32 status, VisaHandle visaObject)
   at NationalInstruments.VisaNS.Session.CheckStatusAndThrow(Int32 status)
   at NationalInstruments.VisaNS.Session.BufferedReaderService.NationalInstruments.VisaNS.Internal.IBufferedReader.Scan(String scanSpecifier, Int32& count, StringBuilder receiver)
   at NationalInstruments.VisaNS.MessageBasedSessionReader.CommonReadString(String scanString, Int32 count)
   at NationalInstruments.VisaNS.MessageBasedSessionReader.ReadLine()
   at isr.Visa.MessageBasedReader.ReadLine()
   at isr.Visa.GpibSession.ReadLine()
   at isr.Visa.Ieee4882.Instrument.ReadString()
   at isr.Visa.Ieee4882.Instrument._flushRead(). VISA status=Success, "FR, CONNECT", 2008-08-12 00:47:21Z, 2077539717184364
DefaultSource, Verbose, 8, Flushing GPIB0::26::INSTR write buffers, "FW, CONNECT", 2008-08-12 00:47:21Z, 2077539723797900
DefaultSource, Verbose, 8, , "WRITE, FW, CONNECT", 2008-08-12 00:47:21Z, 2077539731761192
DefaultSource, Error, 2, Flushing GPIB0::26::INSTR write buffers failed: NationalInstruments.VisaNS.VisaException: Timeout expired before operation completed. VISA error code -1073807339 (0xBFFF0015), ErrorTimeout
   at NationalInstruments.VisaNS.Internal.ErrorChecker.CheckStatusAndThrow(Int32 status, VisaHandle visaObject)
   at NationalInstruments.VisaNS.Session.CheckStatusAndThrow(Int32 status)
   at NationalInstruments.VisaNS.Session.BufferedWriterService.NationalInstruments.VisaNS.Internal.IBufferedWriter.WriteLine()
   at NationalInstruments.VisaNS.MessageBasedSessionWriter.WriteLine()
   at isr.Visa.MessageBasedWriter.WriteLine(String queryCommand)
   at isr.Visa.GpibSession.WriteLine(String queryCommand)
   at isr.Visa.Ieee4882.Instrument.WriteLine(String value)
   at isr.Tsp.TspVisaIO.WriteLine(String value)
   at isr.Visa.Ieee4882.Instrument._flushWrite(). VISA status=Success, "WRITE, FW, CONNECT", 2008-08-12 00:47:21Z, 2077539742753448
The first exception above is raised on the session Message Based Reader ReadLine() command.
Note that I check for message available before issuing read.
Note also that VISA NS returns a status code of success:   VISA status=Success (this is what I log above)
The second exception is raised after I try to clear the write buffers using the Message Based Writer command: WriteLine()
Here too VISA reports success.
Note also that the above segment executes in less than one second whereas the time out is set to 30 seconds.
The user runs VISA 4.3 runtime. I am using NationaInstruments.VisaNS 8.1.20.222.
I would be most grateful for some clues as to how to further explore this issue. We have been at it for a few days already and are not seeing any light at the end of this tunnel.
David

Hello David,
It looks like you are not passing any valid handlers in your viUninstallHandler command. Calling viUninstallHandler removes the specified handler from the list of
active handlers on the given session. You can see the exact error information for your error in the picture below.
Useful information can be found in the manual: VISA Programmers Reference Manual Pages 5-146 & 7
Have a great day!
Meghan R
Applications Engineer
National Instruments
Message Edited by Meghan R on 08-15-2008 11:39 AM
Attachments:
ScreenHunter_01 Aug. 15 11.33.gif ‏9 KB

Why do I get startup disk full error even though I have 2 gb free?

Similar Messages

Maybe you are looking for