Currently Being ModeratedMay 21, 2012 4:34 PM (in response to HollidayPhotography)
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.
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?
Currently Being ModeratedMay 21, 2012 4:47 PM (in response to SierraDragon)
Thanks for your reply, Allen. By removing a vault from the Drobo, I am just freeing up some room for more RAW files before having to increase the storage capacity of the Drobo. The Drobo is slow, but it works pretty well as a mass storage device for RAW files. The Aperture library is on my primary internal drive and that is where the heavy lifting occurs (as you know).
I suppose I will just wait out the creation of the new vault. I will assume that activity is actually occurring. I just wish I had left the Show Activity window open before beginning the process. I only have the progress bar to tell me if Aperture is actually doing something and not in a loop.
Currently Being ModeratedMay 21, 2012 5:42 PM (in response to HollidayPhotography)
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.
Currently Being ModeratedMay 22, 2012 8:41 AM (in response to Frank Caggiano)
Thanks for your advice. I didn't realize that the vault is a package like the library. After poking around, I couldn't find files that had been updated recently. So, I did a force quit of Aperture, rebooted, and repaired the library as you suggested. I am now in the process of creating the new vault once again. I'll post a reply when I have a chance to check in on the progress of the vault creation. Hopefully, things will be going a bit more quickly this time.
Currently Being ModeratedMay 25, 2012 10:32 AM (in response to Frank Caggiano)
Okay, it took forever (well, actually about 48 hours), but the new vault creation actually finished. My guess is that the memory leak was sabotaging the task and it might never have finished. So, big thanks for suggesting the reboot and library repair. That seems to have done the trick.