Error while relocating (Can’t write file (no space))

Question

Level 1

5 points

Error while relocating (Can’t write file (no space))

When I try to relocate masters, I get the above message with seemingly random images

Can't figure out pattern, but console shows this every time:

2/23/10 12:48:05 PM [0x0-0x10a10a].com.apple.Aperture[1969] Tue Feb 23 12:48:05 SilverWolf.local Aperture[1969] <Error>: CGImageCreate: invalid image size: 0 x 0.
2/23/10 12:48:05 PM [0x0-0x10a10a].com.apple.Aperture[1969] Tue Feb 23 12:48:05 SilverWolf.local Aperture[1969] <Error>: CGImageProviderCreate: invalid image provider size: 0.000000 x 0.000000.

Any help>?

Macbook Pro 17 unibody 4gb, Mac OS X (10.6.2), Aperature 3.0

Posted on Feb 23, 2010 1:02 PM

Reply

Answer 1

civilpooch Author

Level 1

5 points

Feb 24, 2010 12:18 PM in response to civilpooch

This is still a problem.

I have over 100GB free.

I can not relocate masters, or export masters, or create a new library with project.

Certain photos cause Aperture 3 to squak about disk space.

Reply

Answer 2

civilpooch Author

Level 1

5 points

Feb 25, 2010 10:14 AM in response to civilpooch

-------------------------------------------------------------------------------- ---------

The EXACT same files can be EXPORTED OK, CONSOLIDATED OK, and don't show any missing files.

The problem is when I try to MOVE the masters from inside the library to outside the library.

I reported this to http://www.apple.com/feedback/aperture.html today

3.0.1 did NOT address this particular issue

Reply

Answer 3

Feb 26, 2010 7:08 PM in response to civilpooch

I'm having the same problem in Aperture 2.

If i click continue relocating it does but i have to click "Ok" for every picture and its kind of complicated when you want to move over 10,000.
I already relocated 5,000 and had no problem but now it won't let me relocate any other.

Any ideas?

Reply

Answer 4

dani190

Level 1

0 points

Mar 4, 2010 8:45 PM in response to civilpooch

any ideas if there is a fix to this? I am having this issue also now...

Reply

Answer 5

uiui

Level 1

0 points

Mar 23, 2010 2:00 AM in response to dani190

Same problem!!!!!

Reply

Answer 6

uiui

Level 1

0 points

Apr 1, 2010 12:13 AM in response to uiui

I've tried almost everything, but no solution, so what do you think if we export the files we would like to relocate and then we'll import again choosing the external HD we wanted as the new destination for our managed files?

Reply

Answer 7

EmuX

Level 1

10 points

Apr 14, 2010 1:54 PM in response to civilpooch

Same Problem. Moreover I never received answer on my question on tether
with D300s on Aperture 3.
I paid a professional software to have all these problems.
And it is better don't cite all the problems about Aperture 3 stability when retouching RAW images.
It is very irritating. 199 plus 99 euros....

Reply

Answer 8

Apr 14, 2010 2:34 PM in response to civilpooch

What format is the drive? If it is FAT32, that is to say, if you do not recall EXPLICITLY formatting it from your Mac after your purchased it, I'd bet it's got a FAT32 file system which is all kinds of broken when you try and use it from Aperture. It simply cannot support Aperture's naming scheme.

Reply

Answer 9

civilpooch Author

Level 1

5 points

Apr 21, 2010 6:20 PM in response to William Lloyd

No, any drives in use are all formatted as default mac journaled.

Reply

Answer 10

AxMstrLP

Level 1

5 points

Apr 21, 2010 8:56 PM in response to William Lloyd

I'm having the same problem. The format of the destination file system shouldn't matter. If you're relocating the masters they are (or will be) referenced. There are no special files associated with the master images itself. All of the "special files" are in the library itself.

In my case, I happen to be moving my masters from a linux file server to a different linux file server. The destination file system is ext3. The volume is mounted over AFP and has 3.5 TB of free space on it. The source drive has 500GB of free space and my boot/system drive has 300GB of space on it so space is definitely not the issue. I suspect Aperture is misreporting the error.

Reply

Answer 11

Apr 28, 2010 11:36 PM in response to AxMstrLP

Ran into this issue tonight, and also do not have a fix. Tried repairing my Library, but that didn't help. I'm going to attempt a rebuild tomorrow and I'll post here if anything changes.

I left a Bug Report on the Aperture Feedback page - hopefully they'll get this taken care of soon.

Reply

Answer 12

Apr 29, 2010 7:53 PM in response to Michael Lake

Aperture 3.0.3. dropped today, but upgrading didn't solve this problem for me (bummer!). So, I'm in the middle of a complete export/re-import to see if it helps.

Reply

Answer 13

Mauronic

Level 1

4 points

May 23, 2010 3:35 PM in response to civilpooch

Same problem. Anyone heard anything new on this?

Reply

Answer 14

saisiv

Level 1

0 points

Jul 3, 2010 11:53 AM in response to Mauronic

same issue.

Tried repairing disks, repairing library, restarting moving to a different drive, via a different interface. still get the same message.

http://www.flickr.com/photos/sai/4758376544/

Reply

Answer 15

saisiv

Level 1

0 points

Jul 4, 2010 2:22 PM in response to saisiv

after spending a significant amount of time at the Apple Store in Toronto with some lovely folks, we are no closer to a solution. The Genius bar set up another appointment with a couple more reps for Monday and we are going to attempt to test some more ideas.

In the mean time i tried to re import the images into a bunch of new projects and ran into yet another issue:
http://discussions.apple.com/message.jspa?messageID=11836194#11836194

Reply