ADSM-L

Re: 5.3.2 server

2006-04-25 12:28:52
Subject: Re: 5.3.2 server
From: Josh-Daniel Davis <xaminmo AT OMNITECH DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 25 Apr 2006 11:23:43 -0500
Matt,
I didn't see further replies to this so I thought I'd add my experience
recently.

I have two servers I've been chasing locks/hangs on, mostly related to
REPAIR STGVOL.

One server would hang up every other day.

I waited for a month to get a patch, which was against 5.3.2.4; however,
in haste, I went to 5.3.3.0 which disables the automatic execution of
REPAIR STGVOL by reclaimation.

That server has been stable, without hangs, for 2 weeks.

Now, when things are slow/idle, I can manually run REPAIR STGVOL. I get
about 100 volumes per hour processed. Eventually it will abort due to some
other process holding a lock. When I restart it, it picks up where it left
off. I only have 1000 volumes left to go.

My other server is still at 5.3.2.3. I will skip to 5.3.3 and manually get
the REPAIRs done during known idle times.

I have the eFix for 5.3.2.4. It prevents REPAIR STGVOL from running when
other processes are running.

If you really need the fix, then TSM support could get you to L2 who can
hook you up with the eFix, but I would recommend 5.3.3 and manual runs
during idle times.

Once you're caught up, you really shouldn't have to worry about it for a
while since it's repairing orphans created at 5.1.5 through 5.1.7.1 during
multithreaded diskpool operations.


-Josh

On 06.04.03 at 11:38 matthew.glanville AT KODAK DOT COM wrote:

Date: Mon, 3 Apr 2006 11:38:57 -0400
From: Matthew Glanville <matthew.glanville AT KODAK DOT COM>
Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: 5.3.2 server

I'm still having 5.3.2.3 repair volume hanging problems when it repairs
offsite volumes during reclaimation.

Matthew Glanville
Eastman Kodak Company
Worldwide Information Systems (WWIS)
343 State Street
Rochester NY 14650
585-477-9371

Privacy/Confidential Disclaimer:
The information contained in this e-mail is private and/or confidential.
It is intended only for the use of the named recipient(s).  If you have
received this e-mail in error, please immediately inform the sender and
delete the message.  If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution,
or copying of this communication is strictly prohibited.


<Prev in Thread] Current Thread [Next in Thread>