ko Krastev
IT Consultant
Roger Deschner <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
30.06.2003 19:38
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: Media Faul
gt; Central Data Storage Manager (a.k.a. storman)
> Shell Information Technology International B.V.
> PO Box 1027, 2260 BA Leidschendam, The Netherlands
>
> Tel: +31-70 303 4984
> Email: Marcel.Anthonijsz.at.shell.com
> Internet: http://www.shell.com
>
>
>
> Date:Tue, 2
gy International B.V.
PO Box 1027, 2260 BA Leidschendam, The Netherlands
Tel: +31-70 303 4984
Email: Marcel.Anthonijsz.at.shell.com
Internet: http://www.shell.com
Date:Tue, 26 Aug 2003 19:48:26 +0200
From:"Marcel J.E. Mol" <[EMAIL PROTECTED]>
Subject: Re: How to read LTO cartridg
On Tue, Aug 26, 2003 at 01:14:21PM +0200, Anthonijsz, Marcel M SITI-ITDGE13 wrote:
> Hi *SM'ers,
>
> Does anybody know how to read the LTO Cartridge memory from the LTO cartridge?
Is this the output you would like to see?
Issuing log sense for page 0x0C...
0 - Write Bytes Received befo
Sent by: "ADSM:How to read LTO cartridge memory (was
Re: Media Fault)
Dist Stor Manager"
<[EMAIL PROTECTED]
EDU>
08/26/03 07:14 AM
Please respond
Hi *SM'ers,
Does anybody know how to read the LTO Cartridge memory from the LTO cartridge?
The LTO specs/brochure show an expected life cycle of about 1 million mounts and
recommends replacement after about 5000 loads.
We want to know how close we are to this figure. TSM forgets about mounts as s
On Tue, Jul 01, 2003 at 09:42:30AM -0400, Richard Sims wrote:
> >Question is: Do you possibly know any software capable of extracting info
> >from LTO CM??
> >(I mean of course a program that can be run against a suspected cartridge)
> >
> >Wieslaw
>
> Now, you know you weren't supposed to ask that
>Question is: Do you possibly know any software capable of extracting info
>from LTO CM??
>(I mean of course a program that can be run against a suspected cartridge)
>
>Wieslaw
Now, you know you weren't supposed to ask that question... :-)
My research indicates that vendors don't consider that c
On Mon, 30 Jun 2003 14:30:41 Richard Sims wrote:
"Well, neither applications nor libraries should actually be tracking that
kind of information, given the propensity of removeable media to migrate
and periodically inhabit different locales: such statistical information
about a cartridge should be
> I started out in December 2002 with all new SDLT tapes and a brand-new
> library with new drives. Since then 3 of the new tapes have had this
> "media fault" condition. As I am researching this, I am finding that
> they are among the most heavily used tapes.
>
> ITSM
used much more heavily than others, and they are
> simply wearing out.
>
> I started out in December 2002 with all new SDLT tapes and a brand-new
> library with new drives. Since then 3 of the new tapes have had this
> "media fault" condition. As I am researching this, I am finding
"media fault" condition. As I am researching this, I am finding that
they are among the most heavily used tapes.
ITSM does not give us any decent statistics on this. Useage numbers are
kept for a "volume", not for a "libvol", which is a serious shortcoming.
This mea
>>ANR8302E I/O error on drive DRIVE2 (mt2.0.0.5) (OP=LOCATE, Error
Number=23,
>>CC=0, KEY=03, ASC=14, ASCQ=00,
>...
>>Every week, a different tape is reporting error. ...
>>Tape drives are fine since the same tape reports error on different
drives.
>(*chuckle*) Well, it could mean that all your d
>ANR8302E I/O error on drive DRIVE2 (mt2.0.0.5) (OP=LOCATE, Error Number=23,
>CC=0, KEY=03, ASC=14, ASCQ=00,
...
>Every week, a different tape is reporting error. ...
>Tape drives are fine since the same tape reports error on different drives.
(*chuckle*) Well, it could mean that all your drives
.
-
00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.
-
00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.
-
00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00.00,
Description=An undetermined error has occurred). Refer to Appendix D in
the
'Messages' manual for recommended action.
ANR8359E Media fault d
15 matches
Mail list logo
