"Unable to quarantine" when copying large iPhoto DB

I have a large iPhoto Database, approx. 56 GB.
When I try to copy it to a NAS, the performance of the copy-process is horribly slow (estimated time shown: several days).
In Console I get hundreds of error messages like this:
12.11.12 20:36:14.000 kernel[0]: Finder[200] Unable to quarantine `c5BwOK5RT0mJtLlYgIik6A.apalbum': 22
12.11.12 20:43:52.000 kernel[0]: Finder[200] Unable to quarantine `50uHH8j7T4ORsQBpGAOrEA.apdetected': 22
When I stop the copying process it just hangs and I need to restart Finder.
When copying a single file, e.g. a 7.7GB mov-File, performance is good and now errors are shown.
Any ideas what this could be?
Thanks
Steffen

Hi,
Just my thought.
An iPhoto Library consists of tons of files.
(Go into the Finder, control click the Library and choose Show Packet Contents)
If you copy it, it starts copying all the files inside the Library to the desired destination.
Another issue, at least I am having a similar problem related to Aperture.
Files can have "extra attributes"
(Go into the Terminal and try the command xattr on a file)
What probably is the case here, is that your NAS does not support extra attributes on files.
So when Finder tries to copy, it also tries to copy the extra attributes.
Which apparently is not possible.
I do get the same error in my log on a single file, but it copies it anyway, so it might be that if you leave it copying it might end succesfully after all.
Not sure about that though.
Regards,
Jan

Similar Messages

Finder issues when copying large amount of files to external drive

When copying large amount of data over firewire 800, finder gives me an error that a file is in use and locks the drive up. I have to force eject. When I reopen the drive, there are a bunch of 0kb files sitting in the directory that did not get copied over. This is happens on multiple drives. I've attached a screen shot of what things look like when I reopen the drive after forcing an eject. Sometime I have to relaunch finder to get back up and running correctly. I've repaired permissions for what it's worth.
10.6.8, by the way, 2.93 12-core, 48gb of ram, fully up to date. This has been happening for a long time, just now trying to find a solution

Scott Oliphant wrote:
iomega, lacie, 500GB, 1TB, etc, seems to be drive independent. I've formatted and started over with several of the drives and same thing. If I copy the files over in smaller chunks (say, 70GB) as opposed to 600GB, the problem does not happen. It's like finder is holding on to some of the info when it puts it's "ghost" on the destination drive before it's copied over and keeping the file locked when it tries to write over it.
This may be a stretch since I have no experience with iomega and no recent experience with LaCie drives, but the different results if transfers are large or small may be a tip-off.
I ran into something similar with Seagate GoFlex drives and the problem was heat. Virtually none of these drives are ventilated properly (i.e, no fans and not much, if any, air flow) and with extended use, they get really hot and start to generate errors. Seagate's solution is to shut the drive down when not actually in use, which doesn't always play nice with Macs. Your drives may use a different technique for temperature control, or maybe none at all. Relatively small data transfers will allow the drives to recover; very large transfers won't, and to make things worse, as the drive heats up, the transfer rate will often slow down because of the errors. That can be seen if you leave Activity Monitor open and watch the transfer rate over time (a method which Seagate tech support said was worthless because Activity Monitor was unreliable and GoFlex drives had no heat problem).
If that's what's wrong, there really isn't any solution except using the smaller chunks of data which you've found works.

HT4710 When copy my IPhoto 7.1.5 Library on my desk computer and open it on my laptop w/IPhoto'09, many albums/slideshows are lost because of compulsory "upgrade." Help!

When copy my IPhoto 7.1.5 Library from my IMac and open it on my MacBookPro, which has IPhoto'09, many albums/slideshows are lost because IPhoto '09 insists that I click on 'upgrade' before it will open the 7.1.5 Library. Help!

The library is damaged in some way.
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one.

Copying large iPhoto library to NAS drive - why is it so difficult?

I have a 2009 iMac, and a large iPhoto library (about 15000 images, circa 90 GB in size). I am trying to transfer the library from the iMac's hard drive to a 3TB Western Digital NAS drive (connected via Gigabit Ethernet) that I've just bought, and it's a nightmare.
I've tried a variety of different approaches - dragging and dropping the iPhoto Library package file onto the pictures directory of the new drive, just exporting the images contained in the 'Masters' subdirectory of the package file, and now using iPhoto Library Manager to attempt to pull the images from my current library into a new iPhoto library that I've created on the new drive. Each way seems to be incredibly lengthy - not just several hours, or even overnight (which I'm prepared for), but days and days - with the iPhoto Library Manager approach the import had been running for about 24 hours and was less than a third of the way through before iPhoto crashed and it stalled.
What is more, I also seem to be unable to delete any of the incomplete package files from the directory on the new drive - again, the progress bar just sits there reading 'Deleting 1 file' and doesn't really do anything. The new drive is formatted as Mac Share, and I can otherwise connect to it and browse through the various directories on there, save small files to it etc, without a problem.
What am I doing wrong? Many thanks for any suggestions.
S

Hi Terence, have read a few of your posts in similar threads this morning and am v relieved I did as I was definitely going to do this all wrong!
Having read your advice on referenced libraries, multiplie libraries, and NAS (ie all being bad) I have come up with the following planned approach for my situation but I would like to run it by you if thats ok?
I don't think I am particularly unusual in my scenario - I am an amateur user who has a personal photo lirbary from the last 10 years and expects it to grow pretty darn big in the future given we now seem to take 100 photos a month since having baby last year!
It already takes up 60GB (50%) of my SSD and so it has to go somewhere...the question is where...
However, where I think i may be less usual is that I don't really use events and additional tagging, I just like iPhoto as a viewer, organiser and slideshow.
From your advice to date I now understand that:
- I can't have my library on my NAS (had been plan 1!)
- Referenced libraries are strongly discouraged (plan 2)
- Using multiple lirbaries to split it down is also discouraged (plan 3, although less beneficial given none of them can go on NAS).
- I should use an ext local HD connected to my laptop when I need to access my photos. (should therefore be plan A but....)
The problem I have though is that using a local ext HD is the least appreciated option by my wife as she hates things being plugged into the laptop in the evening when she kidnaps the laptop for reading her forums, and will likely annoy me if I need to keep getting it from a cupboard, and can't stay in the living room with the little one roaming around and grabing everything gadget I own!
Plus, the most likely value in old photos is going to be that one unexepcted moment in the future when I want to bring one up to show a friend and I am away from the house....
SO, what I am thinking of doing is splitting the situation in 2:
- most of my organising, deleting, managing etc as well as obviously my importing, will happen within the first 6 months of taking a photo. Therefore I will have an iPhoto managed library for that. It will live on my local SSD and all will be good.
- and I will export all older photos to my NAS where they will the live from then on (and continue to move the 6 month expiry photos to this each month or two depending on size constraints). I will try and use events in iPhoto to organise everything before I do this, so that the folders will be useful and useable outside of iphoto on the NAS if I ever need to find anything to view.
- I will then re-import these photos into a second library in iPhoto so I keep the slideshow and viewing capabilities (not sure whether this needs to be a separate library, but probably makes things easier for me to see and manage).
If the links in this ever do get broken with iPhoto I am not sure this matters for me? - I could just re-import each folder and select the event name as the folder name. As mentioned, I don't tend to go into minute detail with events, so there won't be that many (ok, in 30 years time this may be more painful...but I imaging by then we will all be machines and there wil be a new way!)
And if I find I also want access to my <6month photos on NAS as well then I will keep a duplicate export of that on NAS (not managed as a libary within iPhoto) and continue to overwrite it with an export each 1-4 weeks depending on how I much I use things.
What do you think? Have you seen anyone take this approach, and can you see any obvious pitfalls from your experience that I am still missing?
Your advice is much appreciated,
cheers
Jon
A final point is that I have lots of photos from my pre-Mac days and these need to be brought together and consolidated into iPhoto and organised before I do my split. I was going to buy iphoto library manager as apprently it is good at finding the duplicates (I will have 1000's due to lazy copying discipline when i was younger) and I was going to use it for managing libraries anyway, but it is $30 and now I don't need all its functions I think I will just use a bespoke programme for finding any duplicates. I don't want to hijack the thread for this, but any recommendations would obviously be appreciated!

'Unable to quarantine' when exporting from Aperture to a NAS

I have scanned a lot of images as TIFF (approx 28.000), and they are on an External Drive, and I imported them into Aperture (3.3) as referenced files.
Now I want to have a a more workable environment, because the TIFF's are 140 MB each.
So the idea is:
- Export from Aperture to a NAS drive
- Create a new Aperture Library and import them (again as referenced files)
The NAS is a WD MyBook Live Duo that is attached to my Time Machine.
The current Aperture Library and the future Aperture Library will be on my iMac's HD.
I just exported 405 images and in the log I see 405 times:
1/3/13 9:29:34.000 PM kernel[0]: Aperture[54224] Unable to quarantine `/Volumes//Pictures/Modellen_Ref_Files/Mulder_Koosje/JHWA_9601M-25.jpg': 22 (error suppressed)
(Time and filename differ ofcourse.)
However all 405 images were indeed exported.
I read the thread :
https://discussions.apple.com/message/20274081#20274081
https://discussions.apple.com/message/20294802#20294802
from Steffen4712
So before continuing with the rest of the 28.000 images I want to make sure that I will not run into problems.
So can somebody explain to me or point me to a discussion so that I can try and understand what this Quarantine thing is trying to do?
Thanks,
Jan

I managed to find a way to get things done without getting the error.
Workflow from the start:
- scanned negatives and stored them as TIFF files on an external HD
- Started Aperture and imported them as referenced files
- added keywords and adjustments
I tried:
- export them as JPG to a NAS drive
This give the error "Unable to quarantine 22 (error suppressed)"
I tried :
- remove extra attribute from TIFF file on external HD (using xattr -c)
- export them as JPG to a NAS drive
This give the error "Unable to quarantine 22 (error suppressed)"
I tried:
- export them as JPG to my HD
- remove extra attribute from JPG (using xattr -c)
- switch to "new" Aperture Library and import them and choosing the NAS as place to store them
This give the error "Unable to quarantine 22 (error suppressed)"
I tried:
- export them as JPG to my HD
- remove extra attribute from JPG (using xattr -c)
- using Finder and copy them to temporary folder on my NAS
- open "new" Aperture Library and import them and choosing the NAS as place to store them (effectively relocating them)
No errors were seen in the system.log
Conlusion, apparently Aperture wants to quarantine them when moving them to the NAS and Finder does not.
Jan

TC and WD500 External drive - Locks up when copying large files

I have a TC with a Western Digital 500GB my Book connected to the USB port on the TC that I use for network Storage. Everything works fine until I try to copy large files or directories from the Finder mounted share. After the copy freezes the external drive can no longer be seen by airport utility. If I look at disks it sees the disk but no partition. I have to power cycle the external drive to have TC see the drive again. Then I disconnect the drive and plug it in directly to the MAC and run disk utility and his repairs the journal. I have to do the repair every time it locks up. Should the external drive be formatted different or does it have to be connected to a USB hub. Or is this just a bug with the TC and afp ?

I have this very same problem.
I tried to copy a 4GB+ folder from the Macbook to the 500GB MyBook attached to my TC and it froze.
Now the the files on the MyBook are invisible when attached to the TC ("0 Items") but are available when the drive is connected directly to the Macbook. I have run disk utility but it hasn't helped. The disk is FAT 32 formatted and the files on the MyBook are still invisible over the network.
When the drive attached to the Macbook directly I can see a 'phantom' file with the same title as the 4GB+ folder I'd tried to copy. This file is "ZERO KB" and it cannot be deleted (error code -43).
Anyone have a clue what is happening here?

Error when copying large (65bg) file to TC

I recently switched to aperture from iphoto and want to move my iphoto library file (65gb) to my time capsule for storage. I am using the hd in the TC for storage now, while my time machine backups go to a new external HD connected to the TC.
Problem is, when I try to copy the iphoto library file I get an error after it has copied 26.7mb. It says
"...can't complete the operation because some data in "iPhoto Library 1" can't be read or written. (Error code -36)"
So I rebuilt the library using iphoto library manager and had it put the new rebuild file on my TC. That worked, but the new file is 40gb instead of 65gb which is freaking me out.
I also tried making a copy to my internal drive to see if the file would copy at all. It did. Then I tried to move that file to the TC and got the same error, again at 26.7mb.
Any thoughts on why I can't copy this file? I have managed to write and read other files to the TC just fine. And the iphoto library file opens fine so it doesn't appear to be corrupt.

Hi Rudolf,
Thanks, I looked into the erro but it does not give any clue what could cause the error. It just says number of error exceeded. I looked into the access database table and data seems fine. Now I am not sure if the error is causing by the reading from access
or writing to the SQL server. Is there a way to find out what is causing the error?
Thanks.
Ripon

Copying hangs when copying large files from DVD

I'm having trouble copying large files (>2GB) from DVDs to my built-in hard drive. When I drag the file icon from the DVD window to the desktop, the progress bar pops up almost immediately, and says "0 KB of 2.3 GB copied" and "Estimated time left: 1 minute" -- and then it just sits there, doing nothing. In some cases, after five minutes or so of inactivity, the copy finally begins... but most of the time it never does. Force-Quit doesn't help; the only way out is to do an emergency restart and try again.
This problem began when I upgraded to Tiger, and several members of my office group have been experiencing the same problem on their own computers as well.
I've poked around the forum looking for answers but the only thing I could find that looked related was a conflict between iSight and some third-party external hard drives... but none of us have iSight, and none of us are using third-party external drives, so clearly that's not the issue we'rehaving.
Any help out there?
iBook G4 Mac OS X (10.4.6)

Michael, I occasionally notice anomolous behaviour when files get dragged between volumes. Mostly the copying window shows an accurate and immediate indication of what's going on, but other times it just looks like nothing's happening, the display never changes, yet, it is in fact copying the files over. Now, if you're copying 2gb files from DVD to HD, it's gonna take some time, more than 5 minutes, so I'm wondering how long you've left it before forcing it to quit?

Error code 8084 when copying large files from VNX servers

Hi,
We are experiencing problems when attempting to copy large files from our central VNX servers (EMC) using the connection format of smb://<host>/. With Mavericks this will be SMB2, presumably. Anything over a few MB in size fails with the error:
The operation can’t be completed because an unexpected error occurred (error code -8084)
Looking in the Console logs we see the following:
kernel[0]: smb2_smb_read_write_fill: len got reduced, must be running low on credits
If we attempt this on OS X Mountain Lion or below we have no problems.
If, with Mavericks, we connect using the format cifs://<host>/ then file transfers work.
Has anyone come across this before? Thinking I should also post a bug...
Cheers,
Ian
IT Infrastructure, Open University, UK

Not helping but others are having the same problem...
http://discussions.apple.com/thread.jspa?messageID=2564624

Unresponsive system when copying large files drive-to-drive (x86_64)

I'm running Arch x86_64 on a quad core Xeon processor/P35 motherboard w/ 4 gigs of RAM. I also have two SATAII, 7200 RPM HDDs. For the most part, Arch is a VERY responsive platform. I am noticing some really odd unresponsiveness that only happens when I copy large files from one hdd to another hdd.
Symptoms:
-Mouse cursor skips (doesn't move smoothly)
-Windows such as firefox or shell don't move smoothly across the screen if I move them
-Keyboard lag - as I type this post ) my fingers are going faster than the text is appearing
Once the copy is finished, everything is normal again. I swear I read someone else reporting this behavior, I just can't find it. Two questions:
1) Is normal for the x86_64 kernel?
2) If not, what can I tweak to remedy it?
EDIT: Ack! Found the post I remembered reading:
http://bbs.archlinux.org/viewtopic.php?id=70525
Last edited by graysky (2009-07-04 10:51:35)

if the file is bigger than 4gig(uncompressed) then u need swap partition, as the first thing it does is copy the file to memory and if it overflows it is bad. then your server is 1/3 options, either server/middle/desktop. if it is server, it doesn't care what framerate u get on X. then there is the timer. I'm running mine at 300 but arch's default should be 1000. the higher it is the more it "checks" what needs to be done with files, events, etc. then there is the file system type and block size factor. if ur block size is really low like me(1024k) then ur hd has to write more times(on and off) just to write out the huge file. so for huge files, format with huge block size(4096k?) so that the hd does less work.
Last edited by darthaxul (2009-07-04 19:49:07)

Time Capsule WiFi stops when copying large files to Windows 7 (Bootcamp) using WiFi

I've got a new Time Capsule (Purchased less than a month ago) and a new Macbook Pro.
I copied a large set of files (large in QTY & some Large in size > 2GB) to my Time Capsule from a Windows 7 computure via a Wired connection.
When I access the time capsule from Mac OS X (10.8.2) I can copy all of the existing files to my Mac without any issue (Time machine also seems to be working fine).
However when use I Bootcamp (Windows 7 Ultimate) from my MacBook (The Time Capsule / Airport software for windows has been installed) I can only copy about 100 MB before the WiFi in the time capsule stops working. The WiFi doesn't just stop working for Windows, it stops working on the actual Time Capsule; I can tell because my phone and iPad both lose their connection and the AirPort Utility on the iPad can't detect the Time Capsule any more.
The issue is reproducable every time with the set of files I am trying to copy.
I've called Apple Support and they said there was nothing they can do to help (It took a long time to even convince some one that this is a supported configuration even though the Technical Specifications of the time capsule clearly state that Windows 7 is supported - http://www.apple.com/timecapsule/specs.html "For AirPort Disk with a USB hard drive - PC with Windows XP (SP3), Windows Vista (SP2), or Windows 7 (SP1)") at which point they told me to take it to a Genius bar. I've subsequently done that and been told that they will not support the Time Capsule because I am trying to connect to it using Bootcamp.
From what I've seen on this forum some people previously had this issue and worked around it by downgrading the firmware. However, since my Time Capsule is new, I am unable to downgrade the firm ware (& it is the latest).
Any suggestions?

No, it's not a Windows driver issue. 1) If it was a Windows driver issue the network copy would drop out on the Windows machine or fail rather than the whole Time Capsule losing WiFi connectivity for all devices in my house. 2) I am able to copy the exact same set of files, via the Time Capsule WiFi, when the files are stored on my PC which is plugged in to the Time Capsule via an Ethernet cable.
It's not a problem copying the same files from another location on my network with the MBP in Bootcamp therefore it' not a windows driver issue and it's not a network IP issue. It's a Firmware issue with the Time Capsule.
At best this is a bug that has been reintroduced in the latest firmware which is why the suggestions have been to downgrade the firm ware.
At worst this is a major security issue with the Time Capsule as copying a set of files from it's hard disk via it's WiFi, using a Windows computer, cause the Time Capsule to be subseptiable and result in a Denial-of-Service.

System hangs when copying large quantity of files from external HD

A little background:
I was having some problems with the original OS (10.4.1), including periodic freezes. I bought the Mac Box Set '09 and installed Snow Leopard (10.6.5), but ran into some problems and in the process had to reformat my internal hard drive. I backed up all of my photos (~16GB), Documents (~1.5GB) and Music (~50GB) on a WD external hard drive (My Passport 750GB).
*The problem*: After the 10.6.5 install, the computer works great (no random freezing when I click around in Finder), but I am having trouble copying files back to the internal HD from the external. I can copy up to about 1GB at a time without any problems, but any time I try to copy more than that, the system hangs (first the spinning disk cursor, then it totally freezes) and I have to do a hard reset. I have tried copying a number of different folders (pictures and music), and the same holds true: small folders with a few files copy without a hitch, but any time I try to copy a lot of files at once: freeze city. This problem occurs whether I am using Finder to copy the files or iPhoto/iTunes to import them.
I have verified both disks using the Disk Utility AND restructured/verified them using DiskWarrior. I also had no problem copying all of my files from My Passport to a second external HD using this MacBook, so I assume the Passport is fine. Is this a physical problem with my internal HD? If so, why can't DiskWarrior or DiskUtility catch it? I just noticed that there is an internal HD recall for this model of macbook, although I have never gotten the question mark on startup that would qualify me for a replacement HD from Apple. Maybe it's a problem with Snow Leopard... I would love to know if anyone has had this problem before or has some advice.
Thanks,
Sam

External USB/FW drives 'falling off' or drives spinning down (going to sleep) and I would assume since you have been running 10.4 that the Passport might be older model, perhaps not the latest firmware, maybe not compatible with Macs and with Snow Leopard.
Obviously you want FW800 but for some, USB worked where FW fails.
Hard Reset: do you have another hard drive to boot from to run Disk Warrior? is that updated to 4.2 or later? you never want to run DW from CD. Else, boot from OS X 10.6.5; or Single User and run FSCK. HFS+ doesn't take kindly to hard restarts even though a Safe Boot helps a little, that isn't as good as FSCK or one of the other options.
Disk Warrior Rebuild is more thorough, but if you hold OPTION while clicking on REBUILD it brings up more choices. And you want to scan the full hard drive.
Going back to Aug/Sept 2009, there were a lot of threads about external hard drive issues. Wish I could point to a good one.

Error message -36 when copying large files from Firewire drive

I have kept several large audio files as backup on an external LaCie Firewire drive. When trying to copying them back, almost all of them starts to copy, then stops and (after a minute or so) report error message -36.
I have run both Apple's Disktools and the latest Diskwarrior, but no errors are reported. I gues the audio files must have become corrupted... What do you suggest that I do? The contain valuable audio information that I really don't want to get lost.
Helge K.

Not helping but others are having the same problem...
http://discussions.apple.com/thread.jspa?messageID=2564624

Error code -36 when copying large file

Aperture (Apple's pro photo software) stores all of it's data (pictures, metadata, etc) in what appears to be a large file called the Library. In fact, it's a large folder with all of the contents hidden so you don't mess around with it. I back this file up periodically to both an internal and external drive. After a hard drive failure and recreating my whole machine, everything seemed fine and Aperture is working normally. I have tried to drag copy my Aperture Library (rebuilt from my Aperture vault, a back up file created by Aperture) file to my internal second drive, a process that takes about 2 hours (300 Gb). The drive I'm copying to has over 451 GB available and was freshly formatted during this rebuild process. A little more that half way through the drag copy I get the following message.
"The Finder cannot complete the operation because some data in “Aperture Library” could not be read or written, (Error code -36)"
Here's what I've done to so far.
1. Aperture has a function to repair permissions and rebuild the file, done both several times.
2. I found (by looking at all 20,000 plus pictures) some corrupt picture files and deleted them, then repeted step one.
3. Tried a duplicate file on the same drive, same error.
Thoughts? Help? I can't find anything on a Mac OS error -36.
By the way, I'm running Mac OS 10.5.8 and Aperture 2.1.4 on a Quad Core G5.

This what it means:
Type -36 error (I/O Errors (bummers)
This file is having difficulty while either reading from the drive or writing to the drive. The file
may have been improperly written data to the drive or the hard drive or disk may be damaged.
This is almost always indicative of a media error (hard error on the disk). Sometimes (rarely) it is transient.
Solutions: Try copying the file to another drive. Use a disk recovery software, such as Disk First Aid to examine the disk. You can try rebooting with all extensions off. Once in a while this will allow you to read the data. The file in question should be restored from a backup that was stored on a different disk. Regular backups can reduce the time to recover from this error.

NMH305 dies when copying large amounts of data to it

I have an NMH305 still set up with the single original 500GB drive.
I have an old 10/100 3COM rackmount switch (the old white one) uplinked to my Netgear WGR614v7 wireless router. I had the NAS plugged into the 3COM switch and everything worked flawlessly. Only problem was it was only running at 100m.
I recently purchased a TRENDnet TEG-S80g 10/100/1000 'green' switch. I basically replaced the 3com with this switch. To test the 1g speeds, I tried a simple drag & drop of about 4g worth of pics to the NAS on a mapped drive. After about 2-3 seconds, the NAS dropped and Explorer said it was no longer accessible. I could ping it, but the Flash UI was stalled.
If I waited several minutes, it could access it again. I logged into the Flash UI and upgraded to the latest firmware, but had the same problem.
I plugged the NAS directly into the Netgear router and transfered files across the wireless without issue. I plugged it back into the green switch and it dropped after about 6-10 pics transfered.
I totally bypassed the switch and plugged it directly into my computer. Verified I can ping & log in to the Flash UI, then tried to copy files and it died again.
It seems to only happend when running at 1g links speeds. The max transfer I was able to get was about 10mbps, but I'm assuming that's limited by the drive write speeds & controllers.
Anyone ran into this before?
TIA!

Hi cougar694u,
You may check this review "click here". This is a thorough review about the Media Hub's Write and Read throughput vs. File Size - 1000 Mbps LAN.
Cheers

"Unable to quarantine" when copying large iPhoto DB

Similar Messages

Maybe you are looking for