I'm seeing certain controllers hit 200% (dp G5 xserve nodes) running
OSX 10.4.4 and Xsan 1.1
fsmpm is going through the roof...
i thought it was some cron jobs run amok, or launchd, then i
suspected the default ard3 build reports setting...
you can look for the 'build_hd_index' process coming from "/System/
Library/CoreServices/RemoteManagement/ARDAgent.app/Contents/Support/
build_hd_index"
failing the controller (moving control to another mdc) seems to work
hmm
-x
On 28-Jul-06, at 6:59 AM, Samuel Pelletier wrote:
Hi,
Yesterday I rebooted a client (also standby MDC) and after the
reboot, the fsmpm process has a CPU usage of about 40% on a xServe
2X2G! The usual load is about 0.1%. I rebooted everything and it is
now back to 0.1%.
The SAN was accessible on the client but I would like to understand
the situation. Does someone know why this process can eat so much
CPU when is it barely noticeable in normal situations?
_______________________________________________
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
