Q: No longer can access folders with /
-
Aug 26, 2016 6:57 AMby Terence Devlin,Because the finder is running on your Mac. A NAS is a entirely different computer with its own OS and file system, and, given that Aperture needs the Library running on a directly connected disk (not networked, as a NAS is), and one that is formatted Mac OS X Extended, Journaled - which the NAS is not - the question is kind of irrelevant. You'll damage the Library if you put it on the NAS and even if it works, it will perform very badly.
-
Aug 26, 2016 11:07 AMby schalliol,Terence, I think you misunderstand. The NAS is running Btrfs, which is a journaled file system. I've been using EXT3 and EXT4 before on the earlier NAS, which are journaled file system that can support these characters. I've been using AFP (Apple File Protocol) as well, which can pass this info on (SMB can't). That has not been a problem.
When I mount the volume to the desktop from the NAS, it works just great. The Finder can see and work with all the files perfectly. What does not work however is seeing those same files inside Aperture.
-
Aug 26, 2016 12:00 PMby Terence Devlin,No I do understand. You're missing the point.
The Aperture library needs to be on a disk formatted Mac OS Extended (Journaled). Not Btrfs. Not EXT3 or EXT 4.
Also, it needs to be on a directly connected disk. Not AFP or anything else. Not networked. Not Wireless.
What the Finder does or does not do is irrelevant. Aperture is not the Finder.
A NAS is a computer with it's own OS and data structures as you are aware. I'm not sure why you expect an Aperture Library to run from a - what? Linux? - computer.
I'm not sure how I can say this more clearly. Even if you fix this issue with the / character and manage to get the library running from the NAS, as some have, it will be very very likely to get corrupted and you risk sever dataloss.
-
Aug 26, 2016 12:04 PMby schalliol,The library is local, but the referenced files are on a NAS, which is where the problem is. I've been doing this on multiple NASes with Aperture since Aperture launched. Referenced files can be remote. Never had an issue with corruption, but again, I don't have the library on the NAS. The whole point of this post was about referenced files from the very first sentence. I appreciate your attempt at help, and I wonder if now that you understand the question you might have ideas for why Aperture cannot see what the Finder can. I suppose it might because it does not use a native file dialog box for import or reference of files.
-
Aug 29, 2016 7:38 AMby Terence Devlin,HelpfulThe whole point of this post was about referenced files from the very first sentence
Well D'Oh! Sorry I missed that rather obvious piece of information, so my apologies for wasting your time.
As the only thing that has changed is the filesystem of this new NAS there must be an incompatibility between that and the SQL database in Aperture. Have a read of this
It's from the Aperture manual and details how to rename files in batches. I would proceed carefully and see if it works on a trial first. Remove the / characters and replace them with an - or and _. See how that goes.
-
Aug 29, 2016 7:41 AMby schalliol,Thanks Terence. I agree that it would be nice to have the library on a NAS because it limits the ability to use Aperture just to the desktop machine, you'd really need a high performance network and device to make that work even if possible.
Since Aperture can't see the files, I think I might try to copy the files to a local volume on my SSD array and rename them in aperture and then move them to the new NAS. Sigh...
