Q: Library Will Not Connect to Images on Remote Drive Since Lion

I did not say it was off topic.  I said there were many topics and posts about using Aperture across more than one Mac, and there are problems whether involving network drives or not.  That was my only point in that regard.

I use a Managed Library primarily, on a dedicated volume on a separate internal drive.  Any user on my Mac Pro could use that Library and pick right up where the last user left off.  In fact that volume and drive could be put in or connected to any other Mac, and everything needed to edit from a prior session would be available.

This is different from a diiscussion of where the Masters are located.  A full Managed Library contains all the adjustment info as well as the Masters.  If both one Aperture Library and its Referenced Masters on another volume are available to different Macs, one at a time, it will work.

The problem is when two or more users/Macs try to use a Library at the same time, and to a lesser extent could be problematic if only Referenced Masters were sought to be used with different Aperture Libraries.

Ernie

Ernie,

you are slightly moving out of the initial topic.

This topic in only concerning the fact that referenced pictures stored on a NFS mount point are not managed correctly by Aperture and are disconnected on each Aperture's restart. That's all for this topic.

Again I can't see how such a professional product could not handle such a case. That's disapointing.

Laurent.

I used to have this problem with Lion and Aperture, my masters are stored on a QNAP NAS server.

Since the upgrade to Aperture 3.2.2 and Lion 10.7.2 the problem has gone away. not sure which one fixed it, I suspect the Aperture 3.2.2.

Cheers

Treb

It was actually Lion 10.7.2. I used to have the same problem.

It's very weird that for some people this still happens... I wonder if it's specific to certain hardware.

Cheers

C.

I think this may be a NFS specific issue?

I have a QNAP TS439 Pro NAS with ext3 fs

I tried AFP and SAMBA before choosing NFS as NFS was the only way of sharing my files reliably with machines that sleep and wake up regularly etc.

My NAS is QNAP TS219P with ext3 fs.

Cheers Treb

But are you using NFS on the MAC to connect to the NAS?

SAMBA, I haven't enabled NFS.

Thank you for the fast responses. I'm happy that I'm not the only guy rating this as bug. I also created a bug report for the NFS issue (I guess I'm not the first). Hopefully Apple get's aware of the issue and fixes it somewhen in 1212 :-)

I also think it is NFS specific. I just did a test using an AFP share on the same NAS. Aperture found them automatically after restarting. So I can at least confirm, it is no problem with AFP. But I did not try CIFS/Samba...

The trouble is just that I did not find a way making AFP work properly with fast user switching and a shared aperture library on a local partition ignoring user rights. AFP drives are mounted for a specific user. So the same path to a master image is invalid for another user on the same machine. Or does anybody know on how to configure AFP for the following scenario?:

- Masters on the NAS

- Two users using the same AP library on the same machine

Sorry if I post this question in the wrong thread. I just post it here, because I can solve that scenario using NFS. But the issue of this thread breaks currently the solution.

btw. my hardware is a brandnew Synologie DS212 with the newest firmware (DM 3.2-1955).

Another way to workaround the NFS issue would be an AppleScript for reconnecting a single master, as this causes the NFS drive to be recognized online again. However, I could not find a matching function in the AppleScript API Reference for reconnecting a master... If somebody knows a way to automate this, it would be really helpful for me, as I stay on NFS.

Regards

Marco