James,
Yes I am using journaling. Nothing has changed that I am aware of. This node
was built specificly to be used for HSM. I see no journal files at all on
the H: drive.

On Wed, Sep 2, 2009 at 10:38 AM, James Choate <jchoate AT chooses1 DOT com> 
wrote:

> Danny,
> Are you are using HSM and Jorurnaling on this particular client?
>
> It looks like the journaling for the H: drive on the client is having
> issues.
>
> Have there been any recent changes made to this client, ie,. HSM
> implemented, Journaling implemented?
>
> ________________________________________
> From: ADSM: Dist Stor Manager [ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Danny
> Blair [tivolidude AT GMAIL DOT COM]
> Sent: Wednesday, September 02, 2009 8:31 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: 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.
>