Manager"
Re: I've got an interesting issue
with ALMS
04/23/2009 08:43
@VM.MARIST.EDU
Subject: Re: [ADSM-L] I've got an interesting issue with ALMS
No virtual I/O.
Assignment policy - gobi, volser ranges 444000-444999
sahara, volser ranges 333000-333999
All others - "shared", whatever that means.
All cleaning tapes start as "CLN
333063.
Fascinating.
TK
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf
> Of Clark, Robert A
> Sent: Wednesday, April 22, 2009 5:00 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: I've got an interesting issue with ALMS
>
Kauffman, Tom
Sent: Wednesday, April 22, 2009 10:33 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] I've got an interesting issue with ALMS
Not enough of a problem to be worth reporting, but a bit of a curiosity,
and I'm wondering if anyone else has seen this.
We have a 3584 logically part
Not enough of a problem to be worth reporting, but a bit of a curiosity, and
I'm wondering if anyone else has seen this.
We have a 3584 logically partitioned by ALMS into two libraries: gobi, with 10
LTO-4 drives and around 150 LTO-4 tapes; and sahara, with 6 LTO-2 drives and
about 250 LTO-2 ta
DSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Wanda Prather
> Sent: Wednesday, March 12, 2008 8:38 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: AW: Interesting problem in MS-Win restoer -- anyone seen
> something like this before?
>
> Good point - I assume a
Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Wanda
Prather
Sent: Wednesday, March 12, 2008 8:38 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: AW: Interesting problem in MS-Win restoer -- anyone seen something
like this before?
Good point - I assume a tape error (one
iginal Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
> Wanda Prather
> Sent: Tuesday, March 11, 2008 4:12 PM
> To: ADSM-L@VM.MARIST.EDU
> Subject: Re: AW: Interesting problem in MS-Win restoer -- anyone seen
> something like this before?
>
&
[EMAIL PROTECTED] On Behalf Of Wanda
Prather
Sent: Tuesday, March 11, 2008 4:12 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: AW: Interesting problem in MS-Win restoer -- anyone seen something
like this before?
Hey Tom,
THAT is an interesting bit of information.
What media is that 38GB file on? Do you k
Hey Tom,
THAT is an interesting bit of information.
What media is that 38GB file on? Do you know the volser?
If I were going to work on it, the first thing I would do is copy that tape
to a different tape and then try the restore again.
W
On 3/11/08, Kauffman, Tom <[EMAIL PROTECTED]>
or Manager [mailto:[EMAIL PROTECTED] On Behalf Of Henrik
Vahlstedt
Sent: Tuesday, March 11, 2008 3:05 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: AW: Interesting problem in MS-Win restoer -- anyone seen something
like this before?
Hello,
Only curious, is this one solved?
//Henrik
-Origin
Hello,
Only curious, is this one solved?
//Henrik
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Stefan
Holzwarth
Sent: 10. mars 2008 20:33
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] AW: Interesting problem in MS-Win restoer -- anyone seen
> -Ursprüngliche Nachricht-
> Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im
> Auftrag von Kauffman, Tom
> Gesendet: Montag, 10. März 2008 15:05
> An: ADSM-L@VM.MARIST.EDU
> Betreff: Interesting problem in MS-Win restoer -- anyone seen
> something like this be
We've been trying to restore a 38 GB file to a Win2003 SP1 server; the restore
comes to a near halt at 31.8 GB.
At the TSM server side (5.5.0.0) we see 'sendw', and if we leave everything
alone the restore continues at an incredibly slow pace (20 MB in 8 hours).
On the client side - CPU utiliza
h Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Nicholas Cassimatis
Sent: vrijdag 19 januari 2007 20:32
To: ADSM-L@VM.MARIST.EDU
Subject: Fw: Interesting...
Does the file still exist on the filesystem? If the file was deleted,
you may want to r
.MARIST.EDU
cc
Subject
Re: Interesting...
Tolev,
I didn't know there was a undocumented parameter to delete the last DB
backup?
Tim
Levi, Ralph wrote:
I had a similar problem with tapes volumes and the AUDIT VOL xxx
FIX=YES repaired it. This might be an avenue to search
Hi,
The option si: Force=yes
Timothy Hughes <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
19.01.2007 21:27
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Re: Interesting...
Tolev,
I didn't know there was a u
Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Svetoslav Tolev
Sent: Friday, January 19, 2007 12:44 PM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Interesting...
This volume may be contains DB Backup.
To delete this you must user del volh with correct parameters.
If this is last DB BAckup you mus
Does the file still exist on the filesystem? If the file was deleted, you
may want to recreate it and see if the audit or delete will work then.
Nick Cassimatis
@VM.MARIST.EDU
Subject: Re: Interesting...
This volume may be contains DB Backup.
To delete this you must user del volh with correct parameters.
If this is last DB BAckup you must use one undocumented parameter.
"Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]>
Sent by: "AD
55
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Interesting...
Hi *SM-ers!
I have got an interesting situation here.
Please have a look at the following entries and TSM's response.
DELETE VOLUME /appl/tsm_lbu1/diskpool1/lbu1_diskpool
Op,
My mistake.
I didn't see that this is DISKPOOL volume.
"Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
19.01.2007 18:55
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
Inter
sage-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
David E Ehresman
Sent: vrijdag 19 januari 2007 18:09
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Interesting...
Try Audit Volume
The problem seems to go away with current code levels.
>>> "Loon, E.J. van - SPLXM&q
Try Audit Volume
The problem seems to go away with current code levels.
>>> "Loon, E.J. van - SPLXM" <[EMAIL PROTECTED]> 1/19/2007 12:02 PM
>>>
Hi *SM-ers!
I have got an interesting situation here.
Please have a look at the following entries and TSM's
Hi *SM-ers!
I have got an interesting situation here.
Please have a look at the following entries and TSM's response.
DELETE VOLUME /appl/tsm_lbu1/diskpool1/lbu1_diskpool_114
ANR2406E DELETE VOLUME: Volume
/appl/tsm_lbu1/diskpool1/lbu1_diskpool_114 still contains data.
Ok, so the volume
logic/process ?
"Kauffman, Tom" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
09/25/2006 03:58 PM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
[ADSM-L] Had an interesting problem crop up on our 3584 last week
It seems that it is possible to open the I/O port door as the library is
performing a lock function on the door. This left the door open and
unable to close because the lock pin (or tab, or whatever) was in the
way.
This was during a checkout script run, and our tape grabber seems to
have been in
I must be missing something. What's interesting number? even whole #?
Sung
"ADSM: Dist Stor Manager" wrote on 09/19/2006
08:54:51 AM:
> ACTIVITY Date Obj
ACTIVITY Date Objects ExaminedUp/Hr
-- -- -
EXPIRATION 2006-09-1936
<---
LOL
if anyone interested the query looks like this :
t
de, then I would avoid that person at all costs.
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Giglio, Paul
Sent: Thursday, September 08, 2005 9:11 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] An interesting lesson to be learned ( all is not what
it
To all of those TSMrs /system admins that have exhausted all of your avenues
trying to fix something only to find out it wasn't even a problem on your
system...
READ ON .
July 15 2005
TSM server is running on a multiple SP-node ( two silver nodes)
One primary and one secondary backup runnin
gt; BLOCK LOCATE
ERROR, VOL=001010, DRIVE=TAPE0 (mt20.1.2.3): Expected BlockID 2145678;
actual locate 0.
And are hopeing a firmware upgrade will possibly help this.
-Original Message-
From: Karel Bos [mailto:[EMAIL PROTECTED]
Sent: 25 June 2003 08:12
To: [EMAIL PROTECTED]
Subject: Re: Interes
written 139338803
MB read 1437640
Cleanings 251
Power on hours 8590
Interesting part is the number of cleanings. Our cleaning tape has been used
19 times in the past 3 years. This drive is a replacement drive put in our
library by IBM to replace a drive with a tape stuck in it.
Regard,
Karel
This
yes it does...i can dig it up and send it to you if
you'd like. :)
-Original Message-
From: Richard Sims <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Tue, 24 Jun 2003 09:06:50 -0400
Subject: Re: Interesting LTO fault's symptom
>According to a memo I received from I
ing this to ASNEEDED would cause them to be cleaned more frequently.
-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2003 8:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Interesting LTO fault's symptom
Interesting. I have had an IBM 3584 library w
ter that can be set at the
drive level within TSM. All of our drives are set to NONE. I wonder if
setting this to ASNEEDED would cause them to be cleaned more frequently.
-Original Message-
From: David Longo [mailto:[EMAIL PROTECTED]
Sent: Monday, June 23, 2003 8:59 PM
To: [EMAIL PR
ridge.) Maybe thses drives/tapes
are REAL clean already!
David B. Longo
System Administrator
Health First, Inc.
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH 321.434.5536
Pager 321.634.8230
Fax:321.434.5509
[EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 06/24/03 08:48AM >>>
ECTED]
Sent: Tuesday, June 24, 2003 7:49 AM
To: [EMAIL PROTECTED]
Subject: Re: Interesting LTO fault's symptom
>Interesting. I have had an IBM 3584 library with (8) LTO1 drives, FC
attached
>for over a year with no problem. Cleaning tape was installed initially and
>autoclean t
>According to a memo I received from IBM, the LTO
>drives do NOT require periodic cleaning.
I would imagine, then, that the memo goes on to describe the
library cleaning tapes as decorative accessories? ;-)
Richard Sims, BU
/O errors,
though I am begining to suspect SAN backups as the
root cause and not the LTO drives.
leonard
-Original Message-
From: "Thach, Kevin" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Date: Tue, 24 Jun 2003 08:35:39 -0400
Subject: Re: Interesting LTO fault's symptom
(bcc: Henrik Wahlstedt)
TH.COM> Subject: Re: Interesting LTO fault's
symptom
>Interesting. I have had an IBM 3584 library with (8) LTO1 drives, FC attached
>for over a year with no problem. Cleaning tape was installed initially and
>autoclean turned on on the library. Tape has not been used yet!. I backup
>nearly 700GB of data a day and make offsite copies.
003 8:59 PM
To: [EMAIL PROTECTED]
Subject: Re: Interesting LTO fault's symptom
Interesting. I have had an IBM 3584 library with
(8) LTO1 drives, FC attached for over a year with
no problem. Cleaning tape was installed initially
and autoclean turned on on the library. Tape has not
been use
Interesting. I have had an IBM 3584 library with
(8) LTO1 drives, FC attached for over a year with
no problem. Cleaning tape was installed initially
and autoclean turned on on the library. Tape has not
been used yet!. I backup nearly 700GB of data
a day and make offsite copies. Don't do
gt;Sent: Monday, 16 June 2003 9:44 PM
>To: [EMAIL PROTECTED]
>Subject: Interesting LTO fault's symptom
>
>
>Hi all,
>
>during last weeks I did interesting findings at one of production LTO
>3583-L18 library. There are 2 drives and both was changed past
>series of
>
f Wieslaw Markowiak/Kra/ComputerLand/PL
> Sent: Tuesday, June 17, 2003 10:16 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Interesting LTO fault's symptom
>
>
> Hi,
> I had similar problem, but found the apar dealing with it. If you're also
> getting erro
Hi,
I have also been getting I/O errors on my LTO 3583 since I upgraded to
V5.1.6.1 on Solaris. They generally seem to happen when the tape gets to
about 95% capacity. They go to READONLY status but appear to be quite
readable so I dont worry about them as they eventually expire and become
scratch
PROTECTED]
Kopie:
Thema: Re: Interesting LTO fault&
Hi,
I had similar problem, but found the apar dealing with it. If you're also
getting errors like
ANR8302E I/O error on drive MT1.0.0.0 (MT1.0.0.0)
(OP=WRITE, Error Number=1117, CC=400, KEY=4D,
ASC=00,
ASCQ=02,
SENSE=70.00.4D.00.00.00.00.
:[EMAIL PROTECTED]
Sent: 16. júní 2003 14:03
To: [EMAIL PROTECTED]
Subject: Re: Interesting LTO fault's symptom
Could any of you supply your drive firmware level, so we can all compare
notes?
thanks,
bob
On Mon, Jun 16, 2003 at 03:57:47PM +0200, Tom?? Hrouda Ing. wrote:
> We have it on both
Hi,
I was wondering which server hardware do you use.
We had a sort of similar problem with LTO tapes ( Fuji) on Compaq HW, after
disabling the SCSI monitoring agents
the problem disapeared
Mit freundlichen Grüßen / Best Regards
Markus Veit
_
4:42 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Interesting LTO fault's symptom
>
>
> So, we use drive code 28V0, library code 3060,
>
> sorry, for the percentage we do not have 70 but between 20 and 40% as
> percentage utilized at time of the write
:[EMAIL PROTECTED]
Sent: Monday,16. June 2003 16:03
To: [EMAIL PROTECTED]
Subject: Re: Interesting LTO fault's symptom
Could any of you supply your drive firmware level, so we can all compare
notes?
thanks,
bob
On Mon, Jun 16, 2003 at 03:57:47PM +0200, Tom?? Hrouda Ing. wrote:
> We have it
Drive FW 25D4, library 2.80.41 (I think).
Tom
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]
> Behalf Of Bob Booth - UIUC
> Sent: Monday, June 16, 2003 4:03 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Interesting LTO fault's symptom
Manager" <[EMAIL PROTECTED]>
To
[EMAIL PROTECTED]
cc
Subject
Re: Interesting LTO fault's symptom
Could any of you supply your drive firmware level, so we can all compare
notes?
thanks,
bob
On Mon, Jun 16, 2003 at 03:57:47PM +0200, Tom?? Hrouda Ing. wrote:
> We have it
Very Interesting.
I have a 10-drive 3584 library that came with 380 tapes about 22 months
ago. So far, two tapes have locked in drives (which seems to have been a
firmware issue corrected quite some time ago) and one of the tapes was
flawed enough that the drive would die while trying to label
>we have exactly the same problem, about 2 -3 tapes / day with write
>error, 2/3 of capacity. Only on Imation tapes, not on IBM ones...
Interesting. LTO divides its tracks into four bands, which it writes
from inner to outer (analogous to optical media).
See http://www.ultrium.com/newsit
ught 1/2 year later).
> Fault tapes are mixed.
>
> Tomas
>
> > -Original Message-
> > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of
> > Lambelet,Rene,VEVEY,GL-CSC
> > Sent: Monday, June 16, 2003 3:13 PM
> > To: [EMAIL PROTECTED]
ene,VEVEY,GL-CSC
> Sent: Monday, June 16, 2003 3:13 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Interesting LTO fault's symptom
>
>
> Hi,
>
> we have exactly the same problem, about 2 -3 tapes / day with write error,
> 2/3 of capacity. Only on Imation tapes, not on IBM
. [mailto:[EMAIL PROTECTED]
Sent: Monday,16. June 2003 14:14
To: [EMAIL PROTECTED]
Subject: Interesting LTO fault's symptom
Hi all,
during last weeks I did interesting findings at one of production LTO
3583-L18 library. There are 2 drives and both was changed past series of
media faults (o
Hi all,
we are using 3583 LTO library with two LTO drives for 5 or 6 months. No
error on tapes until now.
Interesting findings. If some error occur with tapes I will check more
detaily.
Ing. Jozef Zatko
Login a.s.
Dlha 2, Stupava
tel.: (421) (2) 60252618
"Tomáš Hrouda Ing." <[EM
Hi all,
during last weeks I did interesting findings at one of production LTO
3583-L18 library. There are 2 drives and both was changed past series of
media faults (one of them twice) past about 1 year of operation. We have
about 20 "historicaly touched" tapes with average 3-4 write fau
Hi Richard,
I agree - the only problem is the TSM4.1 does not give you any indication of
the actual volume name - the 3.7 server does.
So in order to find out what tape your backup file is located on you will
first need to run a select * from contents where node_name='BLAH' and ..
Does not ma
>Why has this changed i nthe new version - the message is useless and
>actually misleading.
Christo - If you think this message is bad, take a look at its predecessor,
in APAR IY09212.
Because of the (presumed) bad spot on the tape, TSM should have marked the
file as Damaged (which you
Hi everyone,
We ran into a strange problem after upgrading to TSM4.1 on OS/390.
We tried to run a restore of a client file - it failed giving the following
error:
ANS4035W File '/stage/backups/TRANSACTION_SYSTEM_DAILY.11OCT1999.txt.Z'
currently unavailable on server.
When looking at the server s
65 matches
Mail list logo
