[mm2270]

I have the same problem with my Leopard server and I know almost exactly why this is happening. Sadly I can think of NO way to fix this in my own. The fix MUST come from Apple, as AFP sharing under Leopard server has some serious bugs that they need to address.

The problem has to do with incorrect POSIX permissions being applied to files copied to the shares from client systems, or modified by client systems. Here’s an example:

Say you have a share we’ll call it Share 1. Your ACLs are set the way you want them on this share, and you have basic POSIX permissions set to something like admin for owner and staff for group. The actual permissions for each don’t seem to matter much from what I can tell.

User A copies a folder of files to your share, which is spotlight enabled. If you were to do a Get Info on the folder or files in that folder immediately after it was copied in you’d see that the owner is set to the users login name with Read/Write privs, and group would likely be set to Staff – Read Only. If you keep that Get Info window open you will see something that will make you think you’re losing your mind. The owner and group will both suddenly change to “_unknown” With those POSIX permissions in place the folder or files in that folder will [b]NOT[/b] show up in Spotlight searches from a client machine.

Now, there is a quick temporary fix, and I strongly emphasize “temporary” here, which is to use the Propagate Permissions control in Server Admin’s Sharing tab to propagate down the folder structure, making sure to check the “owner name” box when doing so. Yes, you read correctly. Just propagating the ACLs will NOT work in my experience. You need to fix that _unknown for the owner for it to ever show up in Spotlight. The craziest part of this is that as soon as a client opens any file that was fixed this way and saves changes, it reverts back to _unknown for the owner and that file is no longer searchable with spotlight. Doh!

So in essence, spotlight server works fine as long as no-one touches any files 😯 (!) Nice job Apple! Now how about fixing this ridiculous bug?

I welcome anyone out there to verify my findings by doing what I outlined above and posting results. One thing to note, this does not seem to affect shares coming straight off the server HD, only from shares on an external system, such as a RAID chassis. I haven’t figured out what the difference is there, but I’ve never had the issue with a folder shared out from Server HD. YMMV.

[mm2270]

Hi.

Question- Is the drive that houses the share for your users home folders enabled for disk quotas?
I had a similar issue when I first set up my OD master with home directory users. Several of them blew right past the quotas I had set for their accounts. Turns out you need to enable disk quotas on the actual drive that is housing the home directory share in WGM. Note that it can’t be done at the share level, but on the drive or RAID that houses the share.

Try that and see if it works.

Mike

[Author]

Posts