Network groups are "fetching" on Xsan Volumes ONLY through Finder

Question

Level 1

0 points

Network groups are "fetching" on Xsan Volumes ONLY through Finder

We're using an all apple OD infrastracture with 10.7.4 and Xsan 2.3 and for the past year or so have been expiriencing this fetching issue ever since 10.6.

Not a while ago we've came across Apple's offical article on how-to fix hexadecimal group ID's such as FFFFEEEE-DDDD-CCCC-BBBB-AAAA82000400 from http://support.apple.com/kb/TS3556.

After reading Apple's article we've found out that the problem occures whenever a user logs into the machine BEFORE OD communications is completed.

To get things to work, we usually unmount the Xsan volume and then re-mount whenever the user is ALREADY logged in. This has worked for us for a couple of months till we came across a new problem; After re-mounting we're able to see the right permissions on TERMINAL but on FINDER it's still fetching.

Finder vs. Terminal:

I've tried re-launching Finder without getting lucky, it seems like every time I re-launch Finder a different network group appears as "Fe tching..."

Mac OS X (10.7.5)

Posted on Oct 15, 2012 7:13 AM

Reply

Answer 1

yaform

Level 1

0 points

Oct 29, 2012 7:49 AM in response to tomadmin

This might be a solution:

http://reviews.cnet.com/8301-13727_7-20121641-263/file-group-permissions-constan tly-displaying-fetching..-in-os-x/

Reply

Answer 2

Nov 16, 2012 4:03 AM in response to tomadmin

So the problem occurs when a user logs into a machine before OD communications is completed? Like after startup? Does it happen with 10.7.5?

You might try the solution from http://support.apple.com/kb/TS3556. However, since that script only works in 10.6, replace it with this dumber script:

#!/usr/bin/ruby sleep 60 exec '/Library/Filesystems/Xsan/bin/xsand', *ARGV

This simply causes Xsan startup to be delayed by 60 seconds. If the problem is that OD hasn't finished binding to network directories before the Xsan volume mounts, this might work around the problem. You may need to increase/decrease the sleep time.

Does this help?

Reply

Answer 3

Nov 16, 2012 4:16 AM in response to Blaidd Drwg

Actually the path to xsand changed in 10.7. So the exec command will need to use the new path:

#!/usr/bin/ruby

sleep 60

exec '/System/Library/Filesystems/acfs.fs/Contents/bin/xsand', *ARGV

Reply