Ang: Re: [ADSM-L] Strange behaviour...please Help

2011-10-05 Thread Daniel Sparrman
...@exist.se http://www.existgruppen.se Posthusgatan 1 761 30 NORRTÄLJE -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: Peter Dümpert Sänt av: "ADSM: Dist Stor Manager" Datum: 10/05/2011 16:05 Ärende: Re: [ADSM-L] Strange behaviour...please Help Rober

Re: Strange behaviour...please Help

2011-10-05 Thread Peter Dümpert
Robert, instead of trying q vol 01L2 f=d try the following: q vol 01 f=d i.e. WITHOUT the "L2", i.e,. the 6 char Volser. I assume the "L2" seems to be the appended LTO-type accordingly to Richard Sims' ADSM.Quickfacts with resp. to LTO barcode format Being retir

SV: Strange behaviour...please Help

2011-10-05 Thread Christian Svensson
Cell: +46-70-325 1577 E-mail: christian.svens...@cristie.se Supported Platform for CPU2TSM:: http://www.cristie.se/cpu2tsm-supported-platforms Från: Robert Ouzen [rou...@univ.haifa.ac.il] Skickat: den 4 oktober 2011 19:48 Till: ADSM-L@VM.MARIST.EDU Ämne: Strange b

Re: Strange behaviour...please Help

2011-10-04 Thread Remco Post
Hi Robert, TSM can and will mark a volume as private when a write error is encountered on a scratch volume to prevent reuse. It's worth investigating if that could have been the case. You may find recent cases in the actlog. If you had a defective drive that (possibly) cause this, you could upd

Strange behaviour...please Help

2011-10-04 Thread Robert Ouzen
Hi all I run q libv I2000lib on my library here some of the output: tsm: ADSM>q libv i2000lib Library Name Volume Name Status Owner Last Use HomeDevice Element Typ