Clean installs of 10.3.9, 10.4.2, 10.4.2 Server all exhibit this
symptom on my LAN.
I was referring to a clean, client with a local home directory more so
than the server.
These were clients AND my testing server. All had local home dirs.
The backing store may be the problem as Xsan may not be providing a
device name that the Finder is happy with. At least according to an
Apple SE who has recreated the problem.
It's not particularly special. To the client it's not an XSan volume
but and AFP volume.
But can't the problem be at the AFP server level then, since it's
sharing out the Xsan volume?
More symptoms of the bug:
1. Mount 3 share points, move them all to the dock at once works
fine. Move them one at a time and only the first one stays in the
dock.
Wel that would point more towards a localized object issue at the
Finder end rather than with XSan, AFP, or even sharepoints in general.
Won't argue with that.
2. No bug if sharepoints are mounted via SMB instead of AFP.
3. I actually have 4 servers as part of my Xsan setup (2 MDCs, 2 file
servers). The symptoms occur if I try to mount from any of the
servers.
Point 2 leads me to believe it's an AFP filesystem problem.
It could be a problem with how the APF sharepoint is described and not
be a problem with the AFP sharing,yet alone the /filesystem/. Your
point #1 would suggest this more simply rather than inventing more
complex design issues in a filesystem.
Here's the setup. Xsan volume is called FileRAID. Folders in this
volume called Creative_Services, Commercial, IS_Drive, etc. Xserve
called files. If you have any suggestions as to how to check/change
the AFP sharepoint and how it's described, I'm all ears.
Just not sure if it's on the server or client side, especially if
it's a bug in the client FS on how it handles Xsan volumes.
Well the client isn't seeing an XSan volume. It's seeing an AFP
volume. With AFP volume object descriptors, and the Finder and Dock
are responsible for any mangling those. To the user the backing store
of the sharepoint is already abstracted and the user is ignorant.
Well, I'm ignorant as to where the problem actually lies as well. I'm
just trying to get a fix for it, but have no clue where to really dig
into it. The fact that several other people, including an Apple SE has
reproduced it suggests that it's not just a misconfiguration with my
setup.
Any suggestions?
Stu Duncan
IS Manager
Cox North Carolina Publications, Inc.
(252) 329-9628
email@hidden
http://www.reflector.com
