Hello list,
basically I'm moving this thread http://lists.apple.com/archives/macos-x-server/2007/Nov/msg00883.html to this list because some guys didn't like that I posted it to the macos-x-server list.
The news is that I partialy solved this. I downgraded more than half of the clients to Xsan version 1.4.1 and seems like FSM doesn‘t crash anymore, even when controllers run on 1.4.2. All MDCs are working for couple of days already without a problem. What I‘ve seen is that the more 1.4.2 clients are in the network, the bigger is possibility for FSM to crash.
This explains why FSM didn‘t crash just right after upgrade because I upgraded controllers only. And only then, when I started to upgrade the clients one by one the week later, FSM crashed when reached critical number of them.
This also explains why FSM didn‘t crash (or crashed less) on non working hours. There are less clients connected during the night.
Also what I noticed is that the more 1.4.2 clients are in the network the more RAM FSM process is using compared to 1.4.1 version. For example eight 1.4.2 clients uses ~600mb of RAM, the same eight 1.4.1 clients uses ~450mb of RAM.
For now I‘ll leave the things as they are now, but this is definetely something wrong with Xsan 1.4.2 update, maybe that‘s because I‘m using mixed PPC and Intel clients/MDCs, or maybe I'm having currupted meta data, and this update only showed that. I don't know.
I also found this http://discussions.apple.com/thread.jspa?threadID=1269754
I'd appreciate if someone with their new findings or with experience on 1.4.2 post it here.
Hope this helps someone.
--
Best Regards,
Vilius Šumskas
LNK TV IT manager
http://www.lnk.lt
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xsan-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xsan-users/email@hidden
This email sent to email@hidden
