ADSM-L

Re: [ADSM-L] ANR8503E

2008-08-07 14:47:53
Subject: Re: [ADSM-L] ANR8503E
From: Steve Stackwick <sstackwick AT JASI DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 7 Aug 2008 14:46:32 -0400
On Thu, Aug 7, 2008 at 2:36 PM, Richard van Denzel <RvanDenzel AT sltn DOT nl> 
wrote:
> You've checked the actlog around the time the error occurred?

Nuthin but the ANR8503E and the message that the volume is being set
to readonly.
>
> You're sure that the volume was not full and no more scratch volumes
> could be assigned (maxscratch)?

Actually, some of the volumes were empty, others were filling.

You also checked that the Windows volume
> had sufficient space for the volume (initially only the space for the
> data in the volume is assigned and the volume will grow as data is
> assigned to the volume)?

Not sure what you mean, exactly, but probably I wasn't clear in the
OP. These are predefined FILE class volumes of 200GB.

An addtional note that just occurred to me, though. We've had this
problem periodically, a volume every month or so. No biggie, we just
changed it back to READWRITE and moved on. Now we've moved the server
and shares a half-mile farther apart (as the crow flies-- as the wire
crawls may be considerably farther), so latency must have something to
do with this issue.

Thanks for the reply!

>
> Met vriendelijke groet, with kind regards,
>
> Richard van Denzel.
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Steve Stackwick
> Sent: 07 August 2008 19:41
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] ANR8503E
>
> Anyone else seeing:
>
> ANR8503E A failure occurred in writing to volume
>
> when writing to a FILE class storage pool volume defined on a Windows
> share? This is TSM 5.5, Windows 2003 SP2 on both the sharing system
> and the TSM server. Strangely enough, there are no entries in either
> the sharing system's event log or the TSM server's event log. The
> volume is changed to readonly by TSM after the error, and the writing
> process (MOVE DATA) dies.
>
> I found a reference to someone else having this problem about a year
> ago, but I never saw an answer. Maybe more people have inflicted this
> pain on themselves by now?
>
> We opened a ticket w/ MS, but w/o any eventlog entries, they seem a
> little dubious.
>
> Steve
>
> --
> Stephen Stackwick
> Jacob & Sundstrom, Inc.
> 401 East Pratt St., Suite 2214
> Baltimore, MD 21202-3003
> (410) 539-1135 * (866) 539-1135
> sstackwick AT jasi DOT com
>



--
Stephen Stackwick
Jacob & Sundstrom, Inc.
401 East Pratt St., Suite 2214
Baltimore, MD 21202-3003
(410) 539-1135 * (866) 539-1135
sstackwick AT jasi DOT com

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