Skip navigation

How long should it take for a new vault to be created?

502 Views 5 Replies Latest reply: May 25, 2012 10:32 AM by HollidayPhotography RSS
HollidayPhotography Level 1 Level 1 (0 points)
Currently Being Moderated
May 21, 2012 1:59 PM

I have a late 2009 27" iMac i7 with 16GB of RAM. I use referenced masters. The masters are located on a Drobo connected with FW 800. The internal drive on the iMac is a 1TB drive. The Aperture library is located on that drive and is 158.39 GB. I have about 110,000 master images. Most of them are RAW files shot with a succession of Nikon bodies (D100, D200, D300, and D400). I am in the process of moving a vault off of the Drobo and onto another external hard drive. I started the vault creation on Friday morning (3 days, 6 hours ago) and Aperture shows that it is still working on it.


I have read the germane threads and have given it over three days now to complete. There is very little, if any, progress on the visual indicator that the task is nearing completion. It shows the job as about halfway done. However, Aperture still shows as responding in the Force Quit menu. Aperture is currently using up 11.2 GB of available RAM. Normally, I don't have any memory swaps. Now, page ins are 13,418,681, page outs are 7,226,523, and swaps are at 43.70 GB. CPU utilization shows Aperture consistently at about 170% of capacity.


I really don't want to force quit Aperture for fear of what state it might leave my database. On the other hand, I need my machine and I can't use it until this process finishes or I force quit it.


How do I know if Aperture is actually doing something or is it stuck in an infinite loop? What are the repercussions of doing a force quit? How long should I wait to see if it will actually finish on its own accord?


Any insights, comments, or solutions would be greatly appreciated.



iMac (27-inch Late 2009), Mac OS X (10.7.4), 16GB, Aperture 3.23, Nikon D700
  • SierraDragon Level 4 Level 4 (2,665 points)



    You are not being ignored. I for one just do not know what to say because it depends on how badly you need the use of the Mac and how at-risk your data are. One thought would be to just use the Mac (letting Aperture page out while other apps use the RAM) but that is a risk if the RAM is frozen for some reason. It does sound like you may have a memory leak.


    HollidayPhotography wrote:


    iMac i7 with 16GB of RAM. I use referenced masters. The internal drive on the iMac is a 1TB drive... ...I am in the process of moving a vault off of the Drobo and onto another external hard drive.


    What I do not understand is what you mean by "moving a vault off the Drobo." I would think that if you are making a new Vault that would involve the internal drive and the new drive, no major interaction with the very slow Drobo except to point to Masters there (I could be wrong).


    Also could some of your files be managed on the Drobo rather than referenced?



  • Frank Caggiano Level 7 Level 7 (22,830 points)

    This does seem like a excessive amount of time. You could look at the vault with the finder to see if any files have been modified recently. The vault is like the library, its a package so if you right click on the vault and do a show package contents you can look around in there and see what the dates are.


    While force quiting Aperture is never great some times are worst then others, some times better. While I have no direct knowledge of the inner workings of Aperture if I had to guess I would say force quitting Aperture while it is updating a vault, while bad for the vault, is probably not to bad for the library.


    If you do decide to stop Aperture I would reboot and then run a library repair right after you do this. Also, again while I have no direct knowledge, I have found that if I run a library repair before doing any vault operations (create or update) my incidents of hangs has dropped to about 0.




More Like This

  • Retrieving data ...

Bookmarked By (0)


  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.