At first glance, the errors below look to me like more of an issue regarding
the TSM Journaling Engine on this client, rather than any HSM component.
When you say 'client is failing', can you give a little more description of
the symptoms which suggest this failure, perhaps some output from your
dsmerror.log file with any relevant errors?

/David Mc
London, UK

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Danny Blair
Sent: 02 September 2009 15:31
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] HSM Node Failing

While I am new to managing TSM, I have tried to research this and have not
found much other than "upgrade to 5.5.2" (we are on 5.5.1). Has anyone else
seen this on you HSM clients?

Client is failing. Event viewer on the client machine is full of

"Journal for fs 'H:' reset:"

and

"Notification buffer overrun monitoring fs 'H:\', journal will be reset."

3.37 GB RAM, 60 GB free on C: anmd at least 200 gb free on each drive.

It was a problem on just one drive (others where apparently working fine),
but just last night it started on another.

It sounds like to me that the server itself is having a problem completing
the clients request.

Any ideas?

Thanks in advance.

No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.409 / Virus Database: 270.13.69/2328 - Release Date: 09/02/09
05:50:00