Aperture slideshow export fails - not enough disk space
hey
aperture 3.0 on Lion on macbook air 2011.
i am trying to export a slideshow I created in aperture (200 files, total several hundred mb plus 1 audi mp3)
however, anything over "ipod touch" resolutions throws the error
Unable to Export Slideshow
Not Enough Free Disk Space.
Free up space on the disk and try again.
I have more than 15 GB free, how could it possibly be the reason?
Any ideas?
and where would this data be stored now? because I cannot find it to delete it to recover that disc space...
my situation is critical... I cannot even open the finder because I have zero disc space left after trying to render out my video from a 1 hour slide show with music.
I was supposed to have this completed by tonight and move onto other editing tasks..
Similar Messages
-
Hyper-V client backups fail - not enough disk space
Freeing up space on the host won't help - you want to make a copy of a 500GB guest to a NAS with 600GB.
If your guest has 500GB an dis only using 50GB why allocate it 500GB?Rod-IT wrote:
Bare metal backup, sounds like it is using CIFS as a windows share - you're going to need 500GB for the system, plus space to make it recoverable. I wouldn't expect you to need 600GB but if it says there isn't enough, there isn't enough.
Do other smaller systems work ok?
Why not look at Veeam free edition or EUB to backup your machines instead?
Yeah the whole "not enough disk space" is boggling me. I'm freeing up some additional space on the C drive of the host atm just to try it and see what happens. I'm also downloading the veeam free... no idea they had a free version. I tried to get funding for the real version but as denied so I'll give this a shot. -
Exporting to external harddrive "not enough disk space"
imac Mac OS X (10.3.9)
I'm having several problems while trying to export my entire iphoto library as a backup to an external harddrive...
The main on is I am getting a "not enough disk space error". There is 95 GB available on the harddrive and the library is approximately 20 GB.
I've been doing it in smaller increments b/c I thought it might be an issue of not enough space on my mac's harddrive as I only have like 6GB left (the reason I'm backing up and deletiing photos) but it gets to a certain point and then says no more.
I've been using the export function, but I've also tried just dragging and dropping them and get the same error.
I'm runnning iphoto 4.0.3.
Of course I've tried restarting to no avail...
Any suggestions would be welcome...
Another issue is the filenames. Of course many have the same names from the camera. Is there a way to get them to automatically put them in folders on the harddrive. I've been doing this manually and it's tiresome.
Finally, is there a way to get it keep the "date created" information. When I look on the harddrive it says they were all created 12/31/1903! That's going to make it very difficult to find something later should I need it...
Thanx so much!
JT< The library is like 30 GB while the pictures are only 20GB.>
If you have rotated, cropped, or edited any pictures in iPhoto, the originals are all kept inside the iPlibrary in case you want to "revert to the originals"... it's good to know it's there, but you are less likely to revert to an original, since there's a reason you edited the pics in the first place.
Anyway, those originals are taking "wasted space" in your iPlibrary.
If you want to reduce the size of the iPlibrary from 30GB to close to 20GB, (because the thumbnails will remains and must), then you should get rid of the superfluous duplicates! I did.
if you want to clean you iPlibrary and get rid of duplicates, you can use iPhoto diet. Free download.
My advice, is do a drop and copy the entire iPlibrary to the external, as suggested by eww, because imagine a day, when the internal HD iPLibrary crashes on you, and becomes not salvageable, you will have a mirror copy, to copy back to your internal drive, with all it's albums, names, favorites ,star ratings etc....... If you export to the external HD, and if your iP library crashes on you.... you are to re-import from scratch.... and you will go %#%^&$&@$$@#
I have been there myself... now I have 3 differents external HD that I back up to. 9 different iPlibraries, and 3 copies of each on 3 separate HD..... Photos are too important to me.....
Reading this discussion group, you see many people writting thing such as "my library is gone what do I do?"
it's not a matter of if but when!
You be the judge...
Michel -
Has anyone received an error message of "there is not enough disk space to complete this operation" when trying to export a photo from iphoto? If so, how did you resolve it?
How much free disk do you have? How many and what size of photos do yu have that you are trying to export?
LN -
Exporting from iPhoto: "Not enough disk space to complete this operation"
Hello. I am trying to compile a quick time slide show. There are 72 photos with a total size of 136mb. I get the error "there is not enough disk space to complete this operation" when I try and Export it to my Desktop. Is there a limitation on size to export to Quicktime slide show? I have never noticed this problem before.
Thanks.Greetings--I may have solved this one myself. I knew I had plenty of HD space (92GB) so that wasnt the problem as the error indicated, so:
1--'poofed' iPhoto icon from the Dock--(don't know what the exact description is, but I removed the iPhoto icon from the Dock and it disappeared in a cloud of poof!).
2--I ran Disc Utility and repaired the HD.
3-- I then did a Restart.
My Export to Quicktime seems to be working okay at the moment with no more error
message so maybe the HD just needed straightening up. If you dont hear from me on here again, consider the problem solved.
Cheers. -
Not enough disk space available on the proxy
Wondering if someone might be able to shed some light here.
Trying to deploy a 16GB flar image, but it fails claiming there is not enough disk space on the proxy, however the proxy appears to have plenty of space in /var:
The error:
Task : Download Image
Task Run ID : 23076
Target : PC->ocproxy-6c657073
Status : FAILED
Result : Failed to download image + combo-S10-v149.flar
Logs :
05/01/2015 01:47:15 PM PDT INFO Task is posted to the Proxy Controller (ocproxy-6c657073), from the Enterprise Controller. (15011)
05/01/2015 01:47:18 PM PDT INFO Task is received by the Proxy Controller. (15012)
05/01/2015 01:47:18 PM PDT INFO ---enter into image task run----
05/01/2015 01:47:18 PM PDT INFO download image combo-S10-v149.flar:osFlarImage:,jsPostInstall.sh:osScript:,osp_status_firstboot.sh:osScript:,
05/01/2015 01:47:53 PM PDT ERROR Not enough disk space available on the proxy to download the file - /var/opt/sun/xvm/proxyImageCache/os/flars/combo-S10-v149.flar.
05/01/2015 01:47:53 PM PDT ERROR Image file does not exist - combo-S10-v149.flar.
05/01/2015 01:47:53 PM PDT ERROR Failed to download the url - /ImageDownload/FileDownload?fileName=/os/flars/combo-S10-v149.flar.
05/01/2015 01:47:53 PM PDT ERROR Failed to download image + combo-S10-v149.flar
root@ocproxy:/# df -h
Filesystem Size Used Available Capacity Mounted on
rpool/ROOT/solaris-1 98G 3.3G 68G 5% /
/devices 0K 0K 0K 0% /devices
/dev 0K 0K 0K 0% /dev
ctfs 0K 0K 0K 0% /system/contract
proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
swap 5.5G 1.7M 5.5G 1% /system/volatile
objfs 0K 0K 0K 0% /system/object
sharefs 0K 0K 0K 0% /etc/dfs/sharetab
/usr/lib/libc/libc_hwcap1.so.1
71G 3.3G 68G 5% /lib/libc.so.1
fd 0K 0K 0K 0% /dev/fd
rpool/ROOT/solaris-1/var
98G 13G 68G 17% /var
swap 5.5G 96K 5.5G 1% /tmp
rpool/VARSHARE 98G 2.6M 68G 1% /var/share
rpool/export 98G 35K 68G 1% /export
rpool/export/home 98G 45K 68G 1% /export/home
Any ideas?
-JDid you format your new drive to MAC OS Extended?
Al -
Clean Install G4 Dual 1 GHz-Not enough Disk Space Error? -SLOW USB copies
HELP puhleeeeze!
This seems to be an issue on various sites with no one being able to figure out what is the cause and a solution. One person stated his problem went away with a fullwipe and clean-reinstall of everything. But this is what I did already.
What is the reason for the "Not Enough Disk Space" error message when both my hard drives have gigs of space available. If I had hair I'd be pulling it out by now! When trying to copy a file to my 2 internal hard drives that have a lot of space available, but only by the USB port?!!
I have a Power Mac G4 Mirrored Door (MDD) Dual 1 GHz with a clean install of 10.5.8 from the Original Mac OS X Leopard DVD. Both internal hard drives are 60GB and 100GB. The hard drives were wiped clean with Disc Utilities and reformatted to Mac OS Extended (Journaled). The Power Mac only has the OS and a few music apps installed. Easily over 30 GB of space left on the the main G4 interal hard drive and about 75 GB on the other internal hard drive.
The error seems to only happen when I connect a USB flash drive to the USB port. I tried to copy a 50MB update to the desktop-"Not Enough Disk Space" error message happened.
I know that the G4 MDD Power Macs only have USB 1.0. Is this a USB 2.0 issue? Another issue is that it has very slow USB speed (dramtically slower than normal USB 1.0 copying of files. And this is only when it is successful. Is it a USB format issue? I know I couldn't get an external USB 2.0 drive to mount on the Power Mac at all. Disc Utilities could see it but it still would not mount. I have a friend who has an older G4 single processor Mac that doesn't experience these issues with its USB 1.0 ports.
Now here's the kicker:
If I put in a CD disc in the DVD/RW drive, it copies with no problems to either hard drive. If I connect to the Power Mac via the ethernet network, files can copy with no problems. But any USB connection - I get a the "Not Enough Disk Space" error message. I know this is an old mac... but it's never been problematic until this latest wipe and update to Leopard 10.5.8.
Is there a solution to this? Any and all help, feedback, comments, thoughts are greatly appreciated in advance!!!Hello everyone,
Ok, I did the ultimate task. I erased the hard drives, AGAIN. Just to start fresh from scratch. Hard drives were erased. Did a new install of Mac OS 10.5. And all was well. I could copy with no problems. I gave the computer to my friend and all was good for a couple of days and then the issue came back again. He couldn't copy anything to his internal hard drives and we received the "Not enough disk space" error message! I was baffled. A complete hard drive erase 2 times, 2 fresh Mac OS 10.5 installs and it works for a few days and then coping to HD we got the same **** problem again! THEN - I remembered that the PRAM battery was dead on this G4 Mirrored-Door Dual 1GHz PowerMac. I had recommended that he get a new battery, because this computer would always have the incorrect date and time after every restart. So with recalling this, I had him reset the PRAM by holding down the CMD+OPT+P+R keys after a restart (start-up Chime). I had him hold the keys for at least 3 start-up-chimes. Soon as the G4 Power Mac started up everything was fine again. He was able to copy files to his hard drives again with the "Not enough disk space" error message.
So everyone! Try zapping your PRAM (resetting the PRAM) and see if this solves your problem. I told my friend to get a new PRAM battery to replace the old one that is completely dead. I have not heard back from him. I will ask him again if the problem has come back.
If that fails: My only other solution would be to consider that it is possible that Mac OS 10.5 has a conflict or issue with the G4 Processors and maybe it is safer to install Mac OS 10.3 or 10.4. Because this problem only has occured after installing Mac OS 10.5, the highest version of the Mac OS the Dual 1GHz Mirrored-Door G4 can be installed.
Cheers,
B -
Disk permissions/not enough disk space Warnings
When trying to export tracks, on one system we use, (using an External FW800 1tb HD) with only about 50gb used, after I hit EXPORT on the menu, It tries to write, then I get a disk permissions warning/not enough disk space. ALl the permission on my disk are set to read and write. Anybody?
sorry for the multiple posts... First two tracks exported fine, then the third track generated the error again. I discovered that track had a / in the track name, which meant the files had a / in the name. Removed the slash by renaming the track. BINGO, problem solved. files on computers can't have / in the file names right... beware of the other characters not allowed.
Hope this helps someone.
Steve -
OS X Mountain Lion Install - Not Enough Disk Space
I am installing OS X Mountain Lion. The download went fine. It rebooted and began the install then failed because there is not enough disk space. The solution is obviously to make more room on the disk.
The problem is that everytime I boot my Macbook now, it takes me immediately into the installation for OS X Mountain Lion. I cant seem to get back into the OS to clean up disk space.
Is there any way to force my Macbook to boot to Snow Leopard again? If not, is there any way to clear up disk space from within the OS X Mountain Lion installer or the OSX Utilities? I'd prefer not to have to wipe my entire Macbook and restore from backup then go through the upgrade again after freeing up disk space.
Thanks,
JGCan't be that, [64bit] as this MacPro I have is fully capable, and is running 64bit.
In fact, as far as memory serves, this one I bought [B.T.O. option] was one of the 1st 64bit offerings made available.
But thanks for weighing in …
Anyone else have a suggestion?
Mac Pro
MacBook Pro
Hardware Overview:
Model Name: Mac Pro
Model Identifier: MacPro2,1
Processor Name: Quad-Core Intel Xeon
Processor Speed: 3 GHz
Number Of Processors: 2
Total Number Of Cores: 8
L2 Cache (per processor): 8 MB
Memory: 24 GB
Bus Speed: 1,33 GHz
Boot ROM Version: MP21.007F.B06
SMC Version (system): 1.15f3
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro3,1
Processor Name: Intel Core 2 Duo
Processor Speed: 2,4 GHz
Number of Processors: 1
Total Number of Cores: 2
L2 Cache: 4 MB
Memory: 4 GB
Bus Speed: 800 MHz
Boot ROM Version: MBP31.0070.B07
SMC Version (system): 1.18f5
Even the graphics capabilities, are in the favor of the MacPro, which I opted for:
ATI Radeon X1900 XT, rather than the default option at the time.
This graphics card is due to be replaced with the newer 5870 upgraded card.
Just have not slipped it in the case, as yet.
But even without the graphics card update, it is still better than the MacBook's graphics capabilities, surely? -
The SCE1010 alert "Not enough disk space"
My SCE1010 show the alert "Not enough disk space" in log.
I find old discuss , someone say can delete the file: /tffs0/SYSTEM/PREVDBG.TXT , because the file is too big.
But I don't confirm delete the file will not effect system work fine.
Could everyone help me to solve the problem ?
Thank you very much.
Log shows:
SCE#>show log | i disk
2012-12-25 00:50:44 | WARN | CPU #000 | Not enough disk space.
2012-12-25 00:50:44 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-26 09:07:57 | WARN | CPU #000 | Not enough disk space.
2012-12-26 09:07:57 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-27 17:40:09 | WARN | CPU #000 | Not enough disk space.
2012-12-27 17:40:09 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-29 01:57:20 | WARN | CPU #000 | Not enough disk space.
2012-12-29 01:57:20 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-30 11:54:34 | WARN | CPU #000 | Not enough disk space.
2012-12-30 11:54:34 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-31 20:51:49 | WARN | CPU #000 | Not enough disk space.
2012-12-31 20:51:49 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-02 05:19:01 | WARN | CPU #000 | Not enough disk space.
2013-01-02 05:19:01 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-03 13:31:12 | WARN | CPU #000 | Not enough disk space.
2013-01-03 13:31:12 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-05 03:28:45 | WARN | CPU #000 | Not enough disk space.
2013-01-05 03:28:45 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-06 13:21:00 | WARN | CPU #000 | Not enough disk space.
2013-01-06 13:21:00 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-07 21:18:05 | WARN | CPU #000 | Not enough disk space.
2013-01-07 21:18:05 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-09 05:00:04 | WARN | CPU #000 | Not enough disk space.
2013-01-09 05:00:04 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-10 14:52:16 | WARN | CPU #000 | Not enough disk space.
2013-01-10 14:52:16 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-12 03:29:34 | WARN | CPU #000 | Not enough disk space.
2013-01-12 03:29:34 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-13 13:01:44 | WARN | CPU #000 | Not enough disk space.
2013-01-13 13:01:44 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-14 21:28:53 | WARN | CPU #000 | Not enough disk space.
2013-01-14 21:28:53 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-16 05:30:58 | WARN | CPU #000 | Not enough disk space.
2013-01-16 05:30:58 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-17 19:43:29 | WARN | CPU #000 | Not enough disk space.
2013-01-17 19:43:29 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-19 02:45:28 | WARN | CPU #000 | Not enough disk space.
2013-01-19 02:45:28 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-20 13:22:47 | WARN | CPU #000 | Not enough disk space.
2013-01-20 13:22:47 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-21 21:14:55 | WARN | CPU #000 | Not enough disk space.
2013-01-21 21:14:55 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-23 05:22:05 | WARN | CPU #000 | Not enough disk space.
2013-01-23 05:22:05 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-24 19:14:35 | WARN | CPU #000 | Not enough disk space.
2013-01-24 19:14:35 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-26 04:01:48 | WARN | CPU #000 | Not enough disk space.
2013-01-26 04:01:48 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-27 12:53:58 | WARN | CPU #000 | Not enough disk space.
2013-01-27 12:53:58 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-28 20:36:09 | WARN | CPU #000 | Not enough disk space.
2013-01-28 20:36:09 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-30 06:03:35 | WARN | CPU #000 | Not enough disk space.
2013-01-30 06:03:35 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-31 18:56:02 | WARN | CPU #000 | Not enough disk space.
2013-01-31 18:56:02 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-02 02:48:06 | WARN | CPU #000 | Not enough disk space.
2013-02-02 02:48:06 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-03 10:55:07 | WARN | CPU #000 | Not enough disk space.
2013-02-03 10:55:07 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-03 11:50:10 | WARN | CPU #000 | Not enough disk space.
2013-02-03 11:50:10 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-04 21:37:16 | WARN | CPU #000 | Not enough disk space.
2013-02-04 21:37:16 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-06 10:44:39 | WARN | CPU #000 | Not enough disk space.
2013-02-06 10:44:39 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-07 18:46:44 | WARN | CPU #000 | Not enough disk space.
2013-02-07 18:46:44 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-09 03:23:55 | WARN | CPU #000 | Not enough disk space.
2013-02-09 03:23:55 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-10 11:36:02 | WARN | CPU #000 | Not enough disk space.
2013-02-10 11:36:02 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-11 19:53:10 | WARN | CPU #000 | Not enough disk space.
2013-02-11 19:53:10 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-13 09:55:40 | WARN | CPU #000 | Not enough disk space.
2013-02-13 09:55:40 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-14 19:57:55 | WARN | CPU #000 | Not enough disk space.
2013-02-14 19:57:55 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-16 04:20:07 | WARN | CPU #000 | Not enough disk space.
2013-02-16 04:20:07 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-17 12:12:19 | WARN | CPU #000 | Not enough disk space.
2013-02-17 12:12:19 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-19 02:09:51 | WARN | CPU #000 | Not enough disk space.
2013-02-19 02:09:51 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-20 09:41:58 | WARN | CPU #000 | Not enough disk space.
2013-02-20 09:41:58 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-21 17:39:08 | WARN | CPU #000 | Not enough disk space.
2013-02-21 17:39:08 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-23 03:21:28 | WARN | CPU #000 | Not enough disk space.
2013-02-23 03:21:28 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-24 11:18:43 | WARN | CPU #000 | Not enough disk space.
2013-02-24 11:18:43 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-26 00:36:10 | WARN | CPU #000 | Not enough disk space.
2013-02-26 00:36:10 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-27 08:13:12 | WARN | CPU #000 | Not enough disk space.
2013-02-27 08:13:12 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-27 14:51:13 | WARN | CPU #000 | Not enough disk space.
2013-03-27 14:51:13 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-28 22:43:19 | WARN | CPU #000 | Not enough disk space.
2013-03-28 22:43:19 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-29 22:44:54 | WARN | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
2013-03-30 07:00:26 | WARN | CPU #000 | Not enough disk space.
2013-03-30 07:00:26 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-31 07:02:00 | WARN | CPU #000 | Available disk space at '/tffs0' is 35MB which is under 45MB. Some management operations may fail to execute.
2013-03-31 21:27:56 | WARN | CPU #000 | Not enough disk space.
2013-03-31 21:27:56 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-02 05:10:02 | WARN | CPU #000 | Not enough disk space.
2013-04-02 05:10:02 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-03 13:57:11 | WARN | CPU #000 | Not enough disk space.
2013-04-03 13:57:11 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-04 21:24:16 | WARN | CPU #000 | Not enough disk space.
2013-04-04 21:24:16 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-05 21:25:51 | WARN | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
2013-04-06 11:11:45 | WARN | CPU #000 | Not enough disk space.
2013-04-06 11:11:45 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-07 18:33:53 | WARN | CPU #000 | Not enough disk space.
2013-04-07 18:33:53 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-09 02:46:02 | WARN | CPU #000 | Not enough disk space.
2013-04-09 02:46:02 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-10 02:47:40 | WARN | CPU #000 | Available disk space at '/tffs0' is 29MB which is under 45MB. Some management operations may fail to execute.
2013-04-10 08:08:00 | WARN | CPU #000 | Not enough disk space.
2013-04-10 08:08:00 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-11 08:09:38 | WARN | CPU #000 | Available disk space at '/tffs0' is 32MB which is under 45MB. Some management operations may fail to execute.
2013-04-11 17:35:16 | WARN | CPU #000 | Not enough disk space.
2013-04-11 17:35:16 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-12 17:36:51 | WARN | CPU #000 | Available disk space at '/tffs0' is 34MB which is under 45MB. Some management operations may fail to execute.
2013-04-13 07:12:46 | WARN | CPU #000 | Not enough disk space.
2013-04-13 07:12:46 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-14 07:14:24 | WARN | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
2013-04-14 12:54:48 | WARN | CPU #000 | Not enough disk space.
2013-04-14 12:54:48 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-15 12:56:25 | WARN | CPU #000 | Available disk space at '/tffs0' is 30MB which is under 45MB. Some management operations may fail to execute.
SCE#>Dear Minja.
I have the same problem
Can you see my dir -r ?
SCE#dir -r
File list for /tffs0/
512 WED AUG 13 19:01:34 2008 DIAG DIR
512 WED AUG 13 19:04:00 2008 SYSTEM DIR
512 WED AUG 13 19:13:50 2008 APP DIR
512 WED AUG 13 19:13:50 2008 IMAGES DIR
512 TUE NOV 18 08:48:18 2008 ENGAGE DIR
18189911 TUE APR 16 23:08:26 2013 RELEASE_.SLI
2356 TUE JUN 02 17:14:46 2009 SCRIPT.TXT
7 File(s) 18194827 bytes
File list for /tffs0/DIAG
512 WED AUG 13 19:01:34 2008 . DIR
512 WED AUG 13 19:01:34 2008 .. DIR
2 File(s) 1024 bytes
File list for /tffs0/SYSTEM
512 WED AUG 13 19:04:00 2008 . DIR
512 WED AUG 13 19:04:00 2008 .. DIR
25643 FRI MAY 03 12:02:50 2013 BOOTLOG.TX2
512 WED AUG 13 19:12:46 2008 BACKUP DIR
25441 MON FEB 11 21:30:54 2013 BOOTLOG.TX3
39115 TUE MAY 14 01:29:42 2013 CONFIG.TXT
25658 FRI MAY 03 12:34:36 2013 BOOTLOG.TX1
0 MON FEB 11 13:48:44 2013 BSPFAIL.TXT
25647 SAT MAY 11 06:01:36 2013 BOOTLOG.TXT
0 WED OCT 07 10:18:02 2009 USRCONST.TXT
512 THU OCT 09 05:31:36 2008 PREVCONF DIR
512 WED OCT 07 10:23:12 2009 PQIINST DIR
12 File(s) 144064 bytes
File list for /tffs0/SYSTEM/BACKUP
512 WED AUG 13 19:12:46 2008 . DIR
512 WED AUG 13 19:12:46 2008 .. DIR
9151426 MON FEB 11 21:29:48 2013 DBG_LOG.DF1
16310 MON FEB 11 13:48:56 2013 FAIL.DFL
4 File(s) 9168760 bytes
File list for /tffs0/SYSTEM/PREVCONF
512 THU OCT 09 05:31:36 2008 . DIR
512 THU OCT 09 05:31:36 2008 .. DIR
39115 MON MAY 13 16:06:16 2013 CONFIG.TX8
39115 MON MAY 13 16:26:16 2013 CONFIG.TX7
39115 MON MAY 13 17:24:02 2013 CONFIG.TX6
39115 MON MAY 13 17:28:44 2013 CONFIG.TX5
39115 MON MAY 13 17:51:52 2013 CONFIG.TX4
39115 TUE MAY 14 00:56:44 2013 CONFIG.TX3
39115 TUE MAY 14 01:13:00 2013 CONFIG.TX2
39115 TUE MAY 14 01:29:46 2013 CONFIG.TX1
39115 MON MAY 13 15:38:40 2013 CONFIG.TX9
11 File(s) 353059 bytes
File list for /tffs0/SYSTEM/PQIINST
512 WED OCT 07 10:23:12 2009 . DIR
512 WED OCT 07 10:23:12 2009 .. DIR
2 File(s) 1024 bytes
File list for /tffs0/APP
512 WED AUG 13 19:13:50 2008 . DIR
512 WED AUG 13 19:13:50 2008 .. DIR
17184659 MON FEB 11 21:48:58 2013 EN37592.SLI
3 File(s) 17185683 bytes
File list for /tffs0/IMAGES
512 WED AUG 13 19:13:50 2008 . DIR
512 WED AUG 13 19:13:50 2008 .. DIR
113609411 MON FEB 11 21:09:14 2013 SEOS.PKG
3 File(s) 113610435 bytes
File list for /tffs0/ENGAGE
512 TUE NOV 18 08:48:18 2008 . DIR
512 TUE NOV 18 08:48:18 2008 .. DIR
647546 TUE MAY 14 00:55:44 2013 MYENGAG2.PQB
580274 TUE MAY 14 01:28:48 2013 BATCH.SER
3673 TUE MAY 14 01:29:38 2013 TEMP.DSS
647559 TUE MAY 14 01:11:58 2013 MYENGAG1.PQB
647347 TUE MAY 14 01:28:44 2013 MYENGAGE.PQB
647557 MON MAY 13 17:50:54 2013 MYENGAG3.PQB
8 File(s) 3174980 bytes
373579776 total bytes used
20791296 total bytes free -
Not enough disk space left error
I am trying to put a video that is in .mov format into imovie HD and then export that into a DVD file so I can burn it and play it on a DVD player. But right away when I try importing it to edit it it says not enough disk space. I have 18 gigs on the hard drive that I am using right now. Is there any way around this or would the file just become that big or what? Thank you beforehand for any information you can provide.
No that doesen't pretain to my problem I am not having a problem burning the disk or with Idvd at all (yet anyways) just importing it to Imovie without a pointless error that makes no sense. Of corse it does talk about skipping imovie completely by using Idvd which is what I am trying to do now but it takes a very very long time for quicktime to convert files of that size. But I will see if it works and post back again.
-
Not enough disk space for app download
Got a message to download X Code update, when I select It says there is not enough disk space. on the drive which has my downloads folder it says I have 2.09GB available is this where the download goes?
REmpty 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.
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 on this page 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. -
Not enough disk space to install sims 2 from app store?
I've seen lots of threads resolving the problem of there not being enough disk space when installing sims by a CD Disk, but I'm trying to download it from the app store so none of them apply.
I have 12 GB of space free on my macbook and the application only needs 7.52 GB.
Ideas?
I keep getting 'not enough disk space available'.
I can't open it from the applications folder rather than the Disk because I haven't been allowed to buy/instal it yet.I have cleared 17 GB of hard disk space and 11 GB of memory space.
The requirements online when installed say 10 GB of hard disk and 4 GB of memory.
I bought my Mac last year so I don't think my system is too old.
Ideas now?
When I get above 17 GB it instals but at the end of the hour long installation it again tells me it failed to download, not mentioning space . -
"Unable to Consolidate Library, not enough disk space on C:\"
This is a very annoying bug and i'm certain it is a software bug and nothing that I can fix on my end without an iTunes update. The goods news, is that it should be very easy to change (I say this as a programmer myself.)
The problem: I do not keep all my mp3's on my internal hard drive. This would be impossible since I have a 60gb ipod and my laptop only has a 60gb drive to begin with -- i'd never be able to hold my library on my laptop without using an external for storage. So in iTunes, I have my preferences setup to store music files on this external drive. It is working great. The actual database file is still stored on C:\ (internal) and this is fine since it is rather small. However, when I choose consolidate library, iTunes thinks for a few minutes and then claims that it is unable to perform the action because there is not enough disk space available on C:\. This is silly for several reasons: 1) iTunes should not be coded such that it copies all files to C:\temp (or wherever it does its temp work for that matter) before copying the files to thier final destination. This is just one extra disk read/write that is unneeded. 2) If, for whatever reason, using the internal drive as a temporary buffer is required, then just copy one song at a time. As long as I have enough free space to copy the largest song that needs to be moved, consilidation should be possible. There is no reason to copy all 60gb of music to the temp, then copy all 60gb to my external drive. Instead, it is much smarter to copy one song at a time (and deleting the copy in the temp folder after you are done with it.) 3) An example: My internal drive has 10gb of free space, my external has 55gb of music and 45gb of free space. My library contains 5gb of music that is located on my internal drive. Even if iTunes were to copy all 5gb to the temp space on c:\ before the final copy operation, this should be able to consolidate without a problem. However, it doesn't. For some reason, iTunes thinks that it has to copy all 60gb of music (including 55gb of music that is not going to move anywhere.)
Recently I started storing all my music on a samba server. Simply changed the itunes preferences once again to point to //ipaddress/sharename and it works great. I can even sync my ipod on my laptop with the songs stored on my samba server without any trouble. However, consilidate library still fails for the same reason.Assuming there are enough space available on the filestore folder? Did you check system log during failure? If possible enable CMS trace, that may help you for further investaigation.
-
"Not enough disk space" when there seems to be
I'm a newbie to iDVD and iMovie (my last Mac was a Performa 6360--still using it for the family budget) and got my daughter a MacBook as a graduation gift. She is using it to combine movie inputs from a wedding/reception that come from digital camreas and a couple of video cameras. We went to Flip4Mac to get the necessary features to import .wmv files (only way we could download one of the vidoe cameras).
Issue: When she tries to import vidoes already on her computer, she gets: "The file could not be imported: There is not enough disk space to import Macintosh HD/Users/julie/pictures/iPhoto Library/Originals/2007/Roll8/CIMG1442.AVI"
Basically the question is how to get more room on her disk to import and to save? She seems to only be able to Save--she can't Save Project as an option because it says she doesn't have enough disk space (she's deleted the trash). Help says you need to have more than 400mb of free space or it gets difficult but the indicator shows 28.8GB free space left...so there seems to be some kind of disconnect?? (Or maybe we're talking apples and oranges?)
On top of that, she also gets the same error message when she tries to burn the project onto a disk???
I went through the first 5 pages of the forum and couldn't see a similar problem, but then I may have not known what to look for?
Any help would be greatly appreciated...she's trying to give the DVD as a Wedding gift--somewhat belated.I'm a newbie to iDVD and iMovie (my last Mac was a Performa 6360--still using it for the family budget) and got my daughter a MacBook as a graduation gift. She is using it to combine movie inputs from a wedding/reception that come from digital camreas and a couple of video cameras. We went to Flip4Mac to get the necessary features to import .wmv files (only way we could download one of the vidoe cameras).
Issue: When she tries to import vidoes already on her computer, she gets: "The file could not be imported: There is not enough disk space to import Macintosh HD/Users/julie/pictures/iPhoto Library/Originals/2007/Roll8/CIMG1442.AVI"
Basically the question is how to get more room on her disk to import and to save? She seems to only be able to Save--she can't Save Project as an option because it says she doesn't have enough disk space (she's deleted the trash). Help says you need to have more than 400mb of free space or it gets difficult but the indicator shows 28.8GB free space left...so there seems to be some kind of disconnect?? (Or maybe we're talking apples and oranges?)
On top of that, she also gets the same error message when she tries to burn the project onto a disk???
I went through the first 5 pages of the forum and couldn't see a similar problem, but then I may have not known what to look for?
Any help would be greatly appreciated...she's trying to give the DVD as a Wedding gift--somewhat belated.
Maybe you are looking for
-
Cisco jabber client for anroid
Dear All; I have created android user under cucm and it works fine only one time if disconnected never connected until i restart all the phone services then it reconnect. I also tested the same on different android phone problem is same. Kindly sugg
-
OS 10.6.8 on documents created by Pages 3 will not open They want a Version 4 while my iMac does not install because it needs 4 Pages 10.7. But I can not install 10.7 because my iMac is not Core2 duo ... Funny dilemma!!
-
Lacie network external drive + AEBS + AEX= wireless bliss? Will this work?
Hey everyone, (Just to get it out of the way, I know you can't use the USB ports on the base stations for external Harddrives) Here's what I'm trying to do. I'd like to beable to have a stand alone wireless external Network harddrive (shown here http
-
Can i stream video from an hd camera to an ipad?
can i stream video from an hd camera to an ipad?
-
Critical field credit block goods issue level
Hi, In our company we do Automatic credit management at at goods issue level. At the moment over a certain credit limit the GI just gets blocked. Now we have requirement where if the payment terms are changed by enduser at the sales order level then