Re: CatalogSearch behaving oddly on various AFP volumes
Re: CatalogSearch behaving oddly on various AFP volumes
- Subject: Re: CatalogSearch behaving oddly on various AFP volumes
- From: Thomas Tempelmann <email@hidden>
- Date: Mon, 9 Mar 2009 13:09:42 +0100
On Mon, Mar 9, 2009 at 12:49, I wrote:
>
> When I execute FSCatalogSearch on these volumes, only the one on the
> OS X Server works, while the other one keeps returning error -1304
> ("Catalog has changed and catalog position record may be invalid").
I think this is a bug in the OS.
Here's why:
After a reboot of the remote computer having this problem, and
re-mounting the volume, FSCatalogSearch worked!
Then I found out two more details:
When I mount something that is not a volume on the remote computer,
but which is a sub-folder, such as the user's home folder, then
FSCatalogSearch fails with the -1304 error. Which makes sense,
somewhat, as FSCatalogSearch won't work on sub-trees but only on the
root of a HFS catalog.
HOWEVER: The VolParms bit indicating whether the vol supports
FSCatalogSearch does still claim that FSCatalogSearch is supported on
a mounted remote vol, even if FSCatalogSearch then fails because the
vol is not a true root on the destination system. This might be
considered a bug. In any case, it is misleading.
BUT here's the bigger bug: The first time, when FSCatalogSearch failed
even on the remote's root vol, I had previously mounted that
computer's home folder first, via opening an alias file. While this
time, when FSCatalogSearch worked, I had mounted the remote root vol
first.
ODD, though: I tried to recreate this effect, by rebooting the remote
Mac, then mounting its home folder again. To verify my previous
findings, I even executed FSCatalogSearch on it - this time even that
worked - no -1304 error despite the fact that this vol is not a root
vol on the actual system.
Wow. This is confusing.
The error -1304 comes up rather randomly after rebooting the remote
computer. But once it appears, it remains coming up without end, even
if I run a FSCatalogSearch locally on the remote computer successfully
at the same time.
So, something is fishy here, but I cannot figure out what the
conditions are that lead to it.
Did anyone follow all this up to here? Did I explain clearly what's happening?
I guess I need some clarification first on what SHOULD work:
Is it safe to assume that FSCatalogSearch should generally function on
remote vol that are non-root items on the remote system, such as home
folders?
--
Thomas Tempelmann, http://www.tempel.org/
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Filesystem-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden