Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Why is iBooks Author using up my scratch disk space?

I have recently created a graphic rich travel publication in iBooks Author on my MacBook Pro 2.4GH laptop. When I started I had 50GB of space available on my hard drive. Two days later I received a warning from iBA that I was running low on disk space. Amazed I checked and found that I had less then 2GB remaining. I wrote to Apple 3 times askaing their advice, and have not even received an acknowledgement.


Eventually my recouse was to back off all the files on my scratch disk, completely reinitialise it and reinstall OSX Lion. My thought were that perhaps someting remained in my system from the old OSX 10.6 that was interefring and causing the problems. A clean install would solve it. I started working once again on the newlt installed system, this time making sure I kept track of the space available at start and finish.


At kick-off I had 157.45GB of spare space, and I then made a few changes to my iBA source file. I rechecked the space available afterwrds and, low and behold. it had fallen 147.29GB. iBA had placed another file on my desktop postscripted with a hyphen. I drop this in the bin, emptied it and rebooted the Mac. On reboot there were a couple of recovered filed folder in the bin, totalling 320MB. I deleted these and rechecked the storage space available. It was 147.8GB an increase equal to the disposale of the duplicate source file plus the recovered items file, but still nearly10GB lesss than when I started.


So where did nearly 10GB of space go?


Well, it seems to me that iBA uses a similar method as Time Machine to save changes to the file so that it is possible to back-track. All well and good, but at least with Time Machine there is the option to switch it off. With iBA there is no such option, and it appears that iBA, instead of saving just the changes made, saves multiple complete copies of the file nd does this using an auto-save facility which also cannot be switched off. Furthermore the save file, unlike a Time Machine file appeares to be a 'hidden file' which cannot manually deleted. The only way it apperas to get the disk space back, is to once again, back up all the files of your hard drive, reinitialse it and reinstall the system. Pretty inconvenient!


Unless, of course, someone knows why this is happening and how I can get my disk space back without having to go to this extreme. My source file is now finished and ready for upload, so won't get any bigger, but the finale count is that my disk space is now down to 137.47GB, which means that iBA has now eaten 20GB of my storage.


I checked with another iBA user and she informs me that she had exactly the same problem, so it's just not some abberation of software clash specifically in my laptop. iBA is a nice applicatio to use, but not if every time I use it I end up havig to erase and restore my laptop.


It also doesn't help that Apple have not responded to three emails have sent them either.


ANY IDEAS ANYONE?

MacBook Pro, Mac OS X (10.7.3), 320GB 2.4GH model

Posted on Mar 8, 2012 9:07 AM

Reply
20 replies

Mar 8, 2012 9:17 AM in response to herman.mitt

What 'versions' configuration are you using in Lion? How many versions of each 'book' are being kept?


I'd say tho, that what your're seeing is typical , but without knowing how big your books are (sorry if I missed that), it's difficult to do anything but speculate.


You should be seeing similar resource demands from iMovie and perhaps Pages - do you have any idea how they behave in this context?

Mar 8, 2012 9:29 AM in response to K T

I don't know what you mean by configuration in Lion. If you mean the OSX version it is Lion 10.7.3.


I am working on only one book which 'is' graphic rich, hence 320MB. I do see similar resource demands from other applications like Final Cut where scratch space is used by the program, however, when I exit the application I don't 'permanently' lose the disk space and have to reinitialse the disk to get it back.


This problem is only occurring when I run iBA. Every other application runs as it used to under Snow Leopard. The main reason I upgraded to Lion was to be able to use iBA, but I am not sure that it was such a good idea!

Mar 8, 2012 9:40 AM in response to kenfromUK

That's not going to help. I am pretty tech savy myself having worked with Macs since 1984. I even have a Mac trainging passport that allowed me to open up and modify/repair Macs. I know my way around them hardware and softearw fairly well, but this problem seems to me to be a program development error. It's a coding error!


Buying more storage space will not help when an application decides to eat up all your disk space and stores in the form of an invisible hidden file somewhere in the system. I have plenty of that on my laptop and external drives in fact 3TB. That how I am able to back off all my laptop files and then restore them. But it loses me a days works doing this and it shouldn't be happening.

Mar 8, 2012 10:26 AM in response to herman.mitt

Herman.mitt - you are smarter and more experienced than me when it comes to Macs, so take what I say with a grain of salt and a smile. It is my observation that iBooks Author works in the background like iWeb (remember iWeb?) they both create a host of working files as you add and modify your primary file. Both take up more space than you think they would or should. One way I remedy this is to periodically save my work and quit out of the program. Then I reboot my computer. It usually comes back with the waste basket full of files. I empty the trash and reopen my program and the file I am working on. It runs well and seems to occupy less space.


I work with photos every day. I reduce the picture in Photoshop to the minimum necessary to look good on the iPad. This saves me space in the long run.


I hope this in someway helps. Buying extra hardware to support an iBA project seems inappropriate. - Fabe

Mar 8, 2012 10:32 AM in response to herman.mitt

I had the same problem. I was working on a media-rich IBA file and saw my hard drive space go from 150GB available to 5GB.


It is the versioning that causes it. It is unbelievable to me that you can't turn this off in IBA. It is mandatory, at least that I can tell. So basically, every single time IBA saves a version of your file, it saves the whole **** thing. For me, with a 1GB file that auto-saved two or three times an hour, you can imagine how quickly even 150GB goes.


The only way I have solved the issue is to eliminate old versions. It is slow and frustrating, but at least it works.


Not sure if you know how to get into the IBA version archive. From memory, open the book in question. Run your mouse pointer right next to the file name in the title bar, and a little triangle should appear. Click to bring up the version archive screen. Then, just click on an old version, and from there you can delete either just that version, or if you hold down the option key (I think) while selecting the version, you can delete that version and all those previous to it.


This was the only way I was able to stop IBA from turning into Pac-Man and eating up my hard drive.

Mar 9, 2012 2:55 AM in response to herman.mitt

Hi Herman. Same Problem and thanks KT - it did solve part of the problem. However - if you (like me) have deleted my first book without removing old versions, it is really bad. Because no access to version cache means permanently lost space. I have had to set a new mac just for iAuthor because I am affraid to open any more books. I am down to 25 GB free space after following guides as to remove old versions. However looking at this picture I should have plenty of free space....the rest has been grapped by iAuthor in a hidden versioning cache somewhere.


User uploaded file


As you can see a lot of GB are missing. And it happened EXACTLY when I started using iBooks Author. Before I knew what was happening I was down to 2GB. Versioning is the cause of this. I have been working with media since 1991 - and there is no other programs that saves versions like this - for a good reason. When dealing with large files you need to know where they are, which version and how many. This is completely unsuited for automatic versioning.


I really need - like you also implied to get access to emty the versioning cache. This is a standard feature of products like Adobe Premiere etc. Because when the cache gets too big, you can empty it.

Mar 13, 2012 11:21 AM in response to herman.mitt

I upgraded to ITB of hard disc and 4Gb memory to solve the problem of lack of disc space.


After working recently with the new version (and the new app) for about an hour it crashed and I lost my work - it reverted to a previous save.


I am now very worried about the stability of the new iBooks author as this never happened before.


My program is 1.1 Gb and I have lots of content to add. I notice in another thread that a 1Gb iBook was recommended.


Are crashes and excessive saving periods related to file size?


Should I remove some chapters and be satisfied with this solution?

Mar 14, 2012 6:39 AM in response to MrBlobby1970

I experienced the same problem - bought a new MacBook Pro - migrated from the old one and then noticed that both drives were almost full (478 GB)


My son diagnosed the problem and deleted the versions via Terminal.


I am now storing the files in dropbox because we are working collaboratively with authors across the country.

Strangely, it does not seem to be gobbling up dropbox space - not sure why, but will certainly keep on eye on it.


Thanks for the tip about deleting versions by option/clicking on the title.

Mar 14, 2012 8:00 AM in response to DigtitaFrog

How do you delete the versions via Terminal?


There is a way to do it safely. Go to the book title in the title bar, click on the triangle to go into version history (like Time Machine UI). Click on the right hand side to zoom out last versions, press Option and click on the last version title to delete all old versions.


I save 100GB ⚠ by doing so for most of my iBooks. Unbelievable.


If you mean the file with ~, that's more like scratch files. You can delete anytime.

Why is iBooks Author using up my scratch disk space?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.