![]() ![]() A second possibility is to install ExtremeZ-IP which installs an AFP server on to your Windows Server and also gives the bonus of supporting Spotlight searches. This is done by using the SMBup installer See it does not officially list Mavericks but I did see at least one report that it still worked. I would agree turning off de-duplication is not a desirable solution, however other possibilities to consider are installing the standard Samba software on a Mac and using that instead of Apple's SMBx software. It is perhaps a bit late but it would have been worth signing up for the public beta of Yosemite and testing that and if needed reporting it as an issue for Yosemite as this will be getting more bug fix attention than Mavericks now. It appears to still affect Mavericks 10.9.5 at least from the lack of any positive reports to the contrary. This is a 'known problem' as discussed on the MacWindows site, see on.html "smbfs_nget: filename.ext - unknown reparse point tag 0x80000013" The reparse point tag listed below is "IO_REPARSE_TAG_DEDUP" Via the system.log, I am also seeing the following error when accessing these deduplicated file shares. "One or more items can't be copied to "Foler" because you don't have permissions to read them. When copying files after the PL attributes have been set by deduplication. Has anyone seen this issue? Have any solutions been found? I know this is at least similar to the issues many Mac users are already experiencing and posting about but I haven't seen it directly linked to deduplication and the attributes written by Windows server. I have tried finder replacements such as Pathfinder but the results are the same. Many of the systems having issues are newer and thus not able to be downgraded to 10.8 or 10.7. Other systems running 10.7 do not experience the same issues and are able to access file server resources without issue. I am however, able to copy these files without issue via the terminal. If you 'stop' the copy operation and retry a few more times, it may eventually work for the specific instance but fail again later. This happens when copying to folders within the current folder tree or copying somewhere to the local system. Once the files get deduplicated, users begin receiving read access errors when copying files (see error1 below). Once the file gets optomized/deduplicated and Windows adds the P & L attributes - sparse and symlink - the Macs running Mavericks begin to have access issues. I have found that files newly written or unoptimized are able to be accessed without issue - read, written, modified, etc. Much of the user content is pulled from shares stored on our Windows Server 2012 fileservers with deduplication enabled. ![]() We have a number of 10.9-10.9.3 - Mavericks - machines installed throughout our facility. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |