Thread: [Mtx-general] StorageTek L20 problems on load
Brought to you by:
elgreen,
robertnelson
Menu
▾
▴
mtx-general
|
From: Thomas B. <th...@tr...> - 2008-01-10 09:29:04
|
Hi all
I have the following tape changer:
server:~# mtx -f /dev/sg0 inquiry
Product Type: Medium Changer
Vendor ID: 'STK '
Product ID: 'L20 '
Revision: '0214'
Attached Changer API: No
It's a StorageTek L20. It has some tapes in it:
server:~# mtx -f /dev/sg0 status
Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
Data Transfer Element 0:Empty
Storage Element 1:Full :VolumeTag=3D000024 =
=20
Storage Element 2:Empty
Storage Element 3:Empty
Storage Element 4:Empty
Storage Element 5:Empty
Storage Element 6:Empty
Storage Element 7:Empty
Storage Element 8:Empty
Storage Element 9:Empty
Storage Element 10:Empty
Storage Element 11:Full :VolumeTag=3D000023 =
=20
Storage Element 12:Full :VolumeTag=3D000022 =
=20
Storage Element 13:Full :VolumeTag=3D000021 =
=20
Storage Element 14:Full=20
Storage Element 15 IMPORT/EXPORT:Empty
Transfering tapes between slots (with mtx transfer) works
well. Somehow, I'm not able to load all the tapes into the
drive:
server:~# mtx -f /dev/sg0 load 1
Loading media from Storage Element 1 into drive 0...
mtx: Request Sense: Long Report=3Dyes
mtx: Request Sense: Valid Residual=3Dno
mtx: Request Sense: Error Code=3D70 (Current)
mtx: Request Sense: Sense Key=3DIllegal Request
mtx: Request Sense: FileMark=3Dno
mtx: Request Sense: EOM=3Dno
mtx: Request Sense: ILI=3Dno
mtx: Request Sense: Additional Sense Code =3D 30
mtx: Request Sense: Additional Sense Qualifier =3D 00
mtx: Request Sense: BPV=3Dno
mtx: Request Sense: Error in CDB=3Dno
mtx: Request Sense: SKSV=3Dno
MOVE MEDIUM from Element Address 1000 to 500 Failed
I get the same error for slot 11, 12 and 14 too. Doing the
same command with slot 14 works fine:
server:~# mtx -f /dev/sg0 load 14
Loading media from Storage Element 14 into drive 0...done
server:~# mtx -f /dev/sg0 status
Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
Data Transfer Element 0:Full (Storage Element 14 Loaded)
[...]
Storage Element 14:Empty
Any idea why I cannot load from the other slots? The
only difference I encounter between the various slots is
that 1, 11, 12 and 13 have a VolumeTag while 14 has not.
After having loaded the tape I get some more errors:
server:~# mtx -f /dev/sg0 unload
Unloading drive 0 into Storage Element 14...Drive needs offline before move
server:~# scsitape -f /dev/st0 offline
cannot open SCSI device '/dev/st0' - Input/output error
server:~# mtx -f /dev/sg0 unload
Unloading drive 0 into Storage Element 14...Drive needs offline before move
server:~# scsitape -f /dev/st0 offline
cannot open SCSI device '/dev/st0' - Input/output error
server:~# scsitape -f /dev/st0 rewind
cannot open SCSI device '/dev/st0' - Input/output error
server:~# mtx -f /dev/sg0 unload
Unloading drive 0 into Storage Element 14...done
server:~# mtx -f /dev/sg0 status
Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
Data Transfer Element 0:Empty
[...]
Apparently, I can only do the unload after having invoked 2
times offline and one time rewind.
The =ABcannot open SCSI device=BB error message appears around
one or two minutes after I have issued the command.
According to strace, the process hangs some seconds on the
following system call:
open("/dev/st0", O_RDWR
While searching the mailing list archives and the FAQ I
found a hint that with some tape changer models the =ABrandom
mode=BB should be enabled. I have the user's guide here and it
doesn't mention anything about a random mode or any tape
changer mode at all. I also don't see any such configuration
option in the tape changers menu.
My software versions:
server:~# mtx --version
mtx version 1.3.11
I'm running Debian 4.0 with a 2.6.18-5-xen-686 kernel. I
have build my own Debian package of mtx with the latest
stable version from the mtx SourceForge download page. I'm
performing all those commands within a Xen Dom0.
Any ideas how I could solve my problems? I'm not really
experienced with tape changers, so I'm at a loss.
Regards, Thomas.
|
|
From: Robert N. <rob...@us...> - 2008-01-12 07:12:25
|
The Additional Sense Code in the error message is "INCOMPATIBLE MEDIUM
INSTALLED". Is the only difference between the tapes the barcode label?
Thomas Bader wrote:
> Hi all
>
> I have the following tape changer:
>
> server:~# mtx -f /dev/sg0 inquiry
> Product Type: Medium Changer
> Vendor ID: 'STK '
> Product ID: 'L20 '
> Revision: '0214'
> Attached Changer API: No
>
> It's a StorageTek L20. It has some tapes in it:
>
> server:~# mtx -f /dev/sg0 status
> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
> Data Transfer Element 0:Empty
> Storage Element 1:Full :VolumeTag=000024
> Storage Element 2:Empty
> Storage Element 3:Empty
> Storage Element 4:Empty
> Storage Element 5:Empty
> Storage Element 6:Empty
> Storage Element 7:Empty
> Storage Element 8:Empty
> Storage Element 9:Empty
> Storage Element 10:Empty
> Storage Element 11:Full :VolumeTag=000023
> Storage Element 12:Full :VolumeTag=000022
> Storage Element 13:Full :VolumeTag=000021
> Storage Element 14:Full
> Storage Element 15 IMPORT/EXPORT:Empty
>
> Transfering tapes between slots (with mtx transfer) works
> well. Somehow, I'm not able to load all the tapes into the
> drive:
>
> server:~# mtx -f /dev/sg0 load 1
> Loading media from Storage Element 1 into drive 0...
> mtx: Request Sense: Long Report=yes
> mtx: Request Sense: Valid Residual=no
> mtx: Request Sense: Error Code=70 (Current)
> mtx: Request Sense: Sense Key=Illegal Request
> mtx: Request Sense: FileMark=no
> mtx: Request Sense: EOM=no
> mtx: Request Sense: ILI=no
> mtx: Request Sense: Additional Sense Code = 30
> mtx: Request Sense: Additional Sense Qualifier = 00
> mtx: Request Sense: BPV=no
> mtx: Request Sense: Error in CDB=no
> mtx: Request Sense: SKSV=no
> MOVE MEDIUM from Element Address 1000 to 500 Failed
>
> I get the same error for slot 11, 12 and 14 too. Doing the
> same command with slot 14 works fine:
>
> server:~# mtx -f /dev/sg0 load 14
> Loading media from Storage Element 14 into drive 0...done
> server:~# mtx -f /dev/sg0 status
> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
> Data Transfer Element 0:Full (Storage Element 14 Loaded)
> [...]
> Storage Element 14:Empty
>
> Any idea why I cannot load from the other slots? The
> only difference I encounter between the various slots is
> that 1, 11, 12 and 13 have a VolumeTag while 14 has not.
>
> After having loaded the tape I get some more errors:
>
> server:~# mtx -f /dev/sg0 unload
> Unloading drive 0 into Storage Element 14...Drive needs offline before move
> server:~# scsitape -f /dev/st0 offline
> cannot open SCSI device '/dev/st0' - Input/output error
> server:~# mtx -f /dev/sg0 unload
> Unloading drive 0 into Storage Element 14...Drive needs offline before move
> server:~# scsitape -f /dev/st0 offline
> cannot open SCSI device '/dev/st0' - Input/output error
> server:~# scsitape -f /dev/st0 rewind
> cannot open SCSI device '/dev/st0' - Input/output error
> server:~# mtx -f /dev/sg0 unload
> Unloading drive 0 into Storage Element 14...done
> server:~# mtx -f /dev/sg0 status
> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
> Data Transfer Element 0:Empty
> [...]
>
> Apparently, I can only do the unload after having invoked 2
> times offline and one time rewind.
>
> The «cannot open SCSI device» error message appears around
> one or two minutes after I have issued the command.
> According to strace, the process hangs some seconds on the
> following system call:
>
> open("/dev/st0", O_RDWR
>
> While searching the mailing list archives and the FAQ I
> found a hint that with some tape changer models the «random
> mode» should be enabled. I have the user's guide here and it
> doesn't mention anything about a random mode or any tape
> changer mode at all. I also don't see any such configuration
> option in the tape changers menu.
>
> My software versions:
>
> server:~# mtx --version
> mtx version 1.3.11
>
> I'm running Debian 4.0 with a 2.6.18-5-xen-686 kernel. I
> have build my own Debian package of mtx with the latest
> stable version from the mtx SourceForge download page. I'm
> performing all those commands within a Xen Dom0.
>
> Any ideas how I could solve my problems? I'm not really
> experienced with tape changers, so I'm at a loss.
>
> Regards, Thomas.
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Mtx-general mailing list
> Mtx...@li...
> https://lists.sourceforge.net/lists/listinfo/mtx-general
>
|
|
From: W B. <ws...@pa...> - 2008-01-12 07:50:05
|
That sounds like the wrong format tape, not the label.
Export the one that works and one that doesn't and see if they look
like the same type of cartridge. Keep in mind on DLT and SDLT, you can
have different densities on the same cartridge format so even if they
physically look the same, they still may be incompatible.
Try tapeinfo or use dmesg output for the drive model to see what the
drive is.
Wes
Robert Nelson wrote:
> The Additional Sense Code in the error message is "INCOMPATIBLE MEDIUM =
> INSTALLED". Is the only difference between the tapes the barcode label=
?
>=20
> Thomas Bader wrote:
>=20
>>Hi all
>>
>>I have the following tape changer:
>>
>>server:~# mtx -f /dev/sg0 inquiry
>>Product Type: Medium Changer
>>Vendor ID: 'STK '
>>Product ID: 'L20 '
>>Revision: '0214'
>>Attached Changer API: No
>>
>>It's a StorageTek L20. It has some tapes in it:
>>
>>server:~# mtx -f /dev/sg0 status
>> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
>>Data Transfer Element 0:Empty
>> Storage Element 1:Full :VolumeTag=3D000024 =
=20
>> Storage Element 2:Empty
>> Storage Element 3:Empty
>> Storage Element 4:Empty
>> Storage Element 5:Empty
>> Storage Element 6:Empty
>> Storage Element 7:Empty
>> Storage Element 8:Empty
>> Storage Element 9:Empty
>> Storage Element 10:Empty
>> Storage Element 11:Full :VolumeTag=3D000023 =
=20
>> Storage Element 12:Full :VolumeTag=3D000022 =
=20
>> Storage Element 13:Full :VolumeTag=3D000021 =
=20
>> Storage Element 14:Full=20
>> Storage Element 15 IMPORT/EXPORT:Empty
>>
>>Transfering tapes between slots (with mtx transfer) works
>>well. Somehow, I'm not able to load all the tapes into the
>>drive:
>>
>>server:~# mtx -f /dev/sg0 load 1
>>Loading media from Storage Element 1 into drive 0...
>>mtx: Request Sense: Long Report=3Dyes
>>mtx: Request Sense: Valid Residual=3Dno
>>mtx: Request Sense: Error Code=3D70 (Current)
>>mtx: Request Sense: Sense Key=3DIllegal Request
>>mtx: Request Sense: FileMark=3Dno
>>mtx: Request Sense: EOM=3Dno
>>mtx: Request Sense: ILI=3Dno
>>mtx: Request Sense: Additional Sense Code =3D 30
>>mtx: Request Sense: Additional Sense Qualifier =3D 00
>>mtx: Request Sense: BPV=3Dno
>>mtx: Request Sense: Error in CDB=3Dno
>>mtx: Request Sense: SKSV=3Dno
>>MOVE MEDIUM from Element Address 1000 to 500 Failed
>>
>>I get the same error for slot 11, 12 and 14 too. Doing the
>>same command with slot 14 works fine:
>>
>>server:~# mtx -f /dev/sg0 load 14
>>Loading media from Storage Element 14 into drive 0...done
>>server:~# mtx -f /dev/sg0 status
>> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
>>Data Transfer Element 0:Full (Storage Element 14 Loaded)
>> [...]
>> Storage Element 14:Empty
>>
>>Any idea why I cannot load from the other slots? The
>>only difference I encounter between the various slots is
>>that 1, 11, 12 and 13 have a VolumeTag while 14 has not.
>>
>>After having loaded the tape I get some more errors:
>>
>>server:~# mtx -f /dev/sg0 unload
>>Unloading drive 0 into Storage Element 14...Drive needs offline before =
move
>>server:~# scsitape -f /dev/st0 offline
>>cannot open SCSI device '/dev/st0' - Input/output error
>>server:~# mtx -f /dev/sg0 unload
>>Unloading drive 0 into Storage Element 14...Drive needs offline before =
move
>>server:~# scsitape -f /dev/st0 offline
>>cannot open SCSI device '/dev/st0' - Input/output error
>>server:~# scsitape -f /dev/st0 rewind
>>cannot open SCSI device '/dev/st0' - Input/output error
>>server:~# mtx -f /dev/sg0 unload
>>Unloading drive 0 into Storage Element 14...done
>>server:~# mtx -f /dev/sg0 status
>> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
>> Data Transfer Element 0:Empty
>> [...]
>>
>>Apparently, I can only do the unload after having invoked 2
>>times offline and one time rewind.
>>
>>The =ABcannot open SCSI device=BB error message appears around
>>one or two minutes after I have issued the command.
>>According to strace, the process hangs some seconds on the
>>following system call:
>>
>>open("/dev/st0", O_RDWR
>>
>>While searching the mailing list archives and the FAQ I
>>found a hint that with some tape changer models the =ABrandom
>>mode=BB should be enabled. I have the user's guide here and it
>>doesn't mention anything about a random mode or any tape
>>changer mode at all. I also don't see any such configuration
>>option in the tape changers menu.
>>
>>My software versions:
>>
>>server:~# mtx --version
>>mtx version 1.3.11
>>
>>I'm running Debian 4.0 with a 2.6.18-5-xen-686 kernel. I
>>have build my own Debian package of mtx with the latest
>>stable version from the mtx SourceForge download page. I'm
>>performing all those commands within a Xen Dom0.
>>
>>Any ideas how I could solve my problems? I'm not really
>>experienced with tape changers, so I'm at a loss.
>>
>>Regards, Thomas.
>>
>>-----------------------------------------------------------------------=
--
>>Check out the new SourceForge.net Marketplace.
>>It's the best place to buy or sell services for
>>just about anything Open Source.
>>http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/market=
place
>>_______________________________________________
>>Mtx-general mailing list
>>Mtx...@li...
>>https://lists.sourceforge.net/lists/listinfo/mtx-general
>> =20
>=20
>=20
>=20
> -----------------------------------------------------------------------=
--
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/market=
place
> _______________________________________________
> Mtx-general mailing list
> Mtx...@li...
> https://lists.sourceforge.net/lists/listinfo/mtx-general
>=20
>=20
|
|
From: Robert N. <rob...@us...> - 2008-01-15 08:15:53
|
W Bauske wrote:
> That sounds like the wrong format tape, not the label.
>
>
I know, that's why I asked him to ensure that the tapes are actually the
same. In his original mail he said that they were the same except that
the ones that didn't work had barcode labels.
> Export the one that works and one that doesn't and see if they look
> like the same type of cartridge. Keep in mind on DLT and SDLT, you can
> have different densities on the same cartridge format so even if they
> physically look the same, they still may be incompatible.
>
> Try tapeinfo or use dmesg output for the drive model to see what the
> drive is.
>
> Wes
>
> Robert Nelson wrote:
>
>> The Additional Sense Code in the error message is "INCOMPATIBLE MEDIUM
>> INSTALLED". Is the only difference between the tapes the barcode label?
>>
>> Thomas Bader wrote:
>>
>>
>>> Hi all
>>>
>>> I have the following tape changer:
>>>
>>> server:~# mtx -f /dev/sg0 inquiry
>>> Product Type: Medium Changer
>>> Vendor ID: 'STK '
>>> Product ID: 'L20 '
>>> Revision: '0214'
>>> Attached Changer API: No
>>>
>>> It's a StorageTek L20. It has some tapes in it:
>>>
>>> server:~# mtx -f /dev/sg0 status
>>> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
>>> Data Transfer Element 0:Empty
>>> Storage Element 1:Full :VolumeTag=000024
>>> Storage Element 2:Empty
>>> Storage Element 3:Empty
>>> Storage Element 4:Empty
>>> Storage Element 5:Empty
>>> Storage Element 6:Empty
>>> Storage Element 7:Empty
>>> Storage Element 8:Empty
>>> Storage Element 9:Empty
>>> Storage Element 10:Empty
>>> Storage Element 11:Full :VolumeTag=000023
>>> Storage Element 12:Full :VolumeTag=000022
>>> Storage Element 13:Full :VolumeTag=000021
>>> Storage Element 14:Full
>>> Storage Element 15 IMPORT/EXPORT:Empty
>>>
>>> Transfering tapes between slots (with mtx transfer) works
>>> well. Somehow, I'm not able to load all the tapes into the
>>> drive:
>>>
>>> server:~# mtx -f /dev/sg0 load 1
>>> Loading media from Storage Element 1 into drive 0...
>>> mtx: Request Sense: Long Report=yes
>>> mtx: Request Sense: Valid Residual=no
>>> mtx: Request Sense: Error Code=70 (Current)
>>> mtx: Request Sense: Sense Key=Illegal Request
>>> mtx: Request Sense: FileMark=no
>>> mtx: Request Sense: EOM=no
>>> mtx: Request Sense: ILI=no
>>> mtx: Request Sense: Additional Sense Code = 30
>>> mtx: Request Sense: Additional Sense Qualifier = 00
>>> mtx: Request Sense: BPV=no
>>> mtx: Request Sense: Error in CDB=no
>>> mtx: Request Sense: SKSV=no
>>> MOVE MEDIUM from Element Address 1000 to 500 Failed
>>>
>>> I get the same error for slot 11, 12 and 14 too. Doing the
>>> same command with slot 14 works fine:
>>>
>>> server:~# mtx -f /dev/sg0 load 14
>>> Loading media from Storage Element 14 into drive 0...done
>>> server:~# mtx -f /dev/sg0 status
>>> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
>>> Data Transfer Element 0:Full (Storage Element 14 Loaded)
>>> [...]
>>> Storage Element 14:Empty
>>>
>>> Any idea why I cannot load from the other slots? The
>>> only difference I encounter between the various slots is
>>> that 1, 11, 12 and 13 have a VolumeTag while 14 has not.
>>>
>>> After having loaded the tape I get some more errors:
>>>
>>> server:~# mtx -f /dev/sg0 unload
>>> Unloading drive 0 into Storage Element 14...Drive needs offline before move
>>> server:~# scsitape -f /dev/st0 offline
>>> cannot open SCSI device '/dev/st0' - Input/output error
>>> server:~# mtx -f /dev/sg0 unload
>>> Unloading drive 0 into Storage Element 14...Drive needs offline before move
>>> server:~# scsitape -f /dev/st0 offline
>>> cannot open SCSI device '/dev/st0' - Input/output error
>>> server:~# scsitape -f /dev/st0 rewind
>>> cannot open SCSI device '/dev/st0' - Input/output error
>>> server:~# mtx -f /dev/sg0 unload
>>> Unloading drive 0 into Storage Element 14...done
>>> server:~# mtx -f /dev/sg0 status
>>> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export )
>>> Data Transfer Element 0:Empty
>>> [...]
>>>
>>> Apparently, I can only do the unload after having invoked 2
>>> times offline and one time rewind.
>>>
>>> The ½cannot open SCSI device╗ error message appears around
>>> one or two minutes after I have issued the command.
>>> According to strace, the process hangs some seconds on the
>>> following system call:
>>>
>>> open("/dev/st0", O_RDWR
>>>
>>> While searching the mailing list archives and the FAQ I
>>> found a hint that with some tape changer models the ½random
>>> mode╗ should be enabled. I have the user's guide here and it
>>> doesn't mention anything about a random mode or any tape
>>> changer mode at all. I also don't see any such configuration
>>> option in the tape changers menu.
>>>
>>> My software versions:
>>>
>>> server:~# mtx --version
>>> mtx version 1.3.11
>>>
>>> I'm running Debian 4.0 with a 2.6.18-5-xen-686 kernel. I
>>> have build my own Debian package of mtx with the latest
>>> stable version from the mtx SourceForge download page. I'm
>>> performing all those commands within a Xen Dom0.
>>>
>>> Any ideas how I could solve my problems? I'm not really
>>> experienced with tape changers, so I'm at a loss.
>>>
>>> Regards, Thomas.
>>>
>>> -------------------------------------------------------------------------
>>> Check out the new SourceForge.net Marketplace.
>>> It's the best place to buy or sell services for
>>> just about anything Open Source.
>>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
>>> _______________________________________________
>>> Mtx-general mailing list
>>> Mtx...@li...
>>> https://lists.sourceforge.net/lists/listinfo/mtx-general
>>>
>>>
>>
>> -------------------------------------------------------------------------
>> Check out the new SourceForge.net Marketplace.
>> It's the best place to buy or sell services for
>> just about anything Open Source.
>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
>> _______________________________________________
>> Mtx-general mailing list
>> Mtx...@li...
>> https://lists.sourceforge.net/lists/listinfo/mtx-general
>>
>>
>>
>
>
>
> -------------------------------------------------------------------------
> Check out the new SourceForge.net Marketplace.
> It's the best place to buy or sell services for
> just about anything Open Source.
> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
> _______________________________________________
> Mtx-general mailing list
> Mtx...@li...
> https://lists.sourceforge.net/lists/listinfo/mtx-general
>
|
|
From: W B. <ws...@pa...> - 2008-01-15 08:51:54
|
Note the second part of my response. This user has limited experience with tape devices so I doubt he has seen the many generations of the various tape devices and related generations of density. I run into users who think DLT tapes written on newer drives will work in older devices because they are physically the same size but we all know that doesn't work. He needs to identify his drive and then we can tell him more about what works or doesn't. When the kernel modules are inserted they give sufficient information to tell what device is connected. tapeinfo also gives similar info about the true device that is connected. Examples of tape density progression: dlt2000->dlt4000->dlt7000->dlt8000->sdlt110/220->sdlt160/320->sdlt300/600->dlt-s4 lto1->lto2->lto3->lto4 You cannot put a newer format tape in a previous generation drive. Mostly you can put a one generation back tape in a newer drive. Some generations are a complete break from previous generations but the manufacturer usually changes the name and cartridge so it is clear they are incompatible. Wes Robert Nelson wrote: > W Bauske wrote: > >>That sounds like the wrong format tape, not the label. >> >> >> > I know, that's why I asked him to ensure that the tapes are actually the > same. In his original mail he said that they were the same except that > the ones that didn't work had barcode labels. > >>Export the one that works and one that doesn't and see if they look >>like the same type of cartridge. Keep in mind on DLT and SDLT, you can >>have different densities on the same cartridge format so even if they >>physically look the same, they still may be incompatible. >> >>Try tapeinfo or use dmesg output for the drive model to see what the >>drive is. >> |
|
From: Anton V. <Anton.Vatcky@Sun.COM> - 2008-01-14 06:26:41
Attachments:
anton.vatcky.vcf
|
G'day Thomas, The L20 libraries can support different media type and drive types in the one box. However, mtx assumes that only one type of media and matching drives is supported. For mtx to work correctly all media and drives must be of the one type in the library. So either DLT or LTO based tape drives and media should be used. The L20 library is happy to support both types of media in the one box, but mtx has no way of knowing which media belongs with which drive. The error message you are receiving seems to indicate this incompatibility between the drive and the media. Another point to consider is ensuring you have cleaning media configured and install in the library. This type of media must contain a valid tape label starting with CLNxxx, where xxx is any number. At the time that a tape mount is requested, the library will determine if the tape drive has indicated it needs cleaning, if this is the case, then the library will instead mount a cleaning tape if one is installed, wait for the cleaning operation to finish and then mount the requested tape into the drive. This can cause mtx to time-out thinking there is a hardware problem as the whole mount operation could take up to 3 minutes to complete. For this reason I recommend you specify a longer time-out value for mtx to ensure this cleaning operation is take into account. Also there is a later version of the L20 library firmware revision code (0215) that correct a few mounting problems, which may benefit you. You can obtain this code at www.support.storagetek.com or contact your local Sun Microsystems office to have a technician upgrade your system for you. I hope this help. Regards, ---- Anton Vatcky Senior Software Engineer Sun Microsystems, Inc. Level 3, 243 Northbourne Avenue Lyneham, ACT 2602 Australia Phone +61 (0)2-6217-5571 Mobile +61 (0)417-412-628 Fax +61 (0)2-6257-2664 Email Anton.Vatcky@Sun.COM Thomas Bader wrote: > Hi all > > I have the following tape changer: > > server:~# mtx -f /dev/sg0 inquiry > Product Type: Medium Changer > Vendor ID: 'STK ' > Product ID: 'L20 ' > Revision: '0214' > Attached Changer API: No > > It's a StorageTek L20. It has some tapes in it: > > server:~# mtx -f /dev/sg0 status > Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export ) > Data Transfer Element 0:Empty > Storage Element 1:Full :VolumeTag=000024 > Storage Element 2:Empty > Storage Element 3:Empty > Storage Element 4:Empty > Storage Element 5:Empty > Storage Element 6:Empty > Storage Element 7:Empty > Storage Element 8:Empty > Storage Element 9:Empty > Storage Element 10:Empty > Storage Element 11:Full :VolumeTag=000023 > Storage Element 12:Full :VolumeTag=000022 > Storage Element 13:Full :VolumeTag=000021 > Storage Element 14:Full > Storage Element 15 IMPORT/EXPORT:Empty > > Transfering tapes between slots (with mtx transfer) works > well. Somehow, I'm not able to load all the tapes into the > drive: > > server:~# mtx -f /dev/sg0 load 1 > Loading media from Storage Element 1 into drive 0... > mtx: Request Sense: Long Report=yes > mtx: Request Sense: Valid Residual=no > mtx: Request Sense: Error Code=70 (Current) > mtx: Request Sense: Sense Key=Illegal Request > mtx: Request Sense: FileMark=no > mtx: Request Sense: EOM=no > mtx: Request Sense: ILI=no > mtx: Request Sense: Additional Sense Code = 30 > mtx: Request Sense: Additional Sense Qualifier = 00 > mtx: Request Sense: BPV=no > mtx: Request Sense: Error in CDB=no > mtx: Request Sense: SKSV=no > MOVE MEDIUM from Element Address 1000 to 500 Failed > > I get the same error for slot 11, 12 and 14 too. Doing the > same command with slot 14 works fine: > > server:~# mtx -f /dev/sg0 load 14 > Loading media from Storage Element 14 into drive 0...done > server:~# mtx -f /dev/sg0 status > Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export ) > Data Transfer Element 0:Full (Storage Element 14 Loaded) > [...] > Storage Element 14:Empty > > Any idea why I cannot load from the other slots? The > only difference I encounter between the various slots is > that 1, 11, 12 and 13 have a VolumeTag while 14 has not. > > After having loaded the tape I get some more errors: > > server:~# mtx -f /dev/sg0 unload > Unloading drive 0 into Storage Element 14...Drive needs offline before move > server:~# scsitape -f /dev/st0 offline > cannot open SCSI device '/dev/st0' - Input/output error > server:~# mtx -f /dev/sg0 unload > Unloading drive 0 into Storage Element 14...Drive needs offline before move > server:~# scsitape -f /dev/st0 offline > cannot open SCSI device '/dev/st0' - Input/output error > server:~# scsitape -f /dev/st0 rewind > cannot open SCSI device '/dev/st0' - Input/output error > server:~# mtx -f /dev/sg0 unload > Unloading drive 0 into Storage Element 14...done > server:~# mtx -f /dev/sg0 status > Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export ) > Data Transfer Element 0:Empty > [...] > > Apparently, I can only do the unload after having invoked 2 > times offline and one time rewind. > > The «cannot open SCSI device» error message appears around > one or two minutes after I have issued the command. > According to strace, the process hangs some seconds on the > following system call: > > open("/dev/st0", O_RDWR > > While searching the mailing list archives and the FAQ I > found a hint that with some tape changer models the «random > mode» should be enabled. I have the user's guide here and it > doesn't mention anything about a random mode or any tape > changer mode at all. I also don't see any such configuration > option in the tape changers menu. > > My software versions: > > server:~# mtx --version > mtx version 1.3.11 > > I'm running Debian 4.0 with a 2.6.18-5-xen-686 kernel. I > have build my own Debian package of mtx with the latest > stable version from the mtx SourceForge download page. I'm > performing all those commands within a Xen Dom0. > > Any ideas how I could solve my problems? I'm not really > experienced with tape changers, so I'm at a loss. > > Regards, Thomas. > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > _______________________________________________ > Mtx-general mailing list > Mtx...@li... > https://lists.sourceforge.net/lists/listinfo/mtx-general > |
|
From: Robert N. <rob...@us...> - 2008-01-15 08:21:13
|
Anton Vatcky wrote: > G'day Thomas, > > The L20 libraries can support different media type and drive types in > the one box. However, mtx assumes that only one type of media and > matching drives is supported. > > For mtx to work correctly all media and drives must be of the one type > in the library. So either DLT or LTO based tape drives and media > should be used. > What are you basing this on? mtx doesn't know or care what type of media or drives are installed. It just sends SCSI commands telling the changer what to do. > The L20 library is happy to support both types of media in the one > box, but mtx has no way of knowing which media belongs with which > drive. The error message you are receiving seems to indicate this > incompatibility between the drive and the media. > It is up to the user to know which tapes are compatible with which drives. > Another point to consider is ensuring you have cleaning media > configured and install in the library. This type of media must > contain a valid tape label starting with CLNxxx, where xxx is any > number. > > At the time that a tape mount is requested, the library will determine > if the tape drive has indicated it needs cleaning, if this is the > case, then the library will instead mount a cleaning tape if one is > installed, wait for the cleaning operation to finish and then mount > the requested tape into the drive. > > This can cause mtx to time-out thinking there is a hardware problem as > the whole mount operation could take up to 3 minutes to complete. For > this reason I recommend you specify a longer time-out value for mtx to > ensure this cleaning operation is take into account. > > Also there is a later version of the L20 library firmware revision > code (0215) that correct a few mounting problems, which may benefit > you. You can obtain this code at www.support.storagetek.com or > contact your local Sun Microsystems office to have a technician > upgrade your system for you. > > I hope this help. > > Regards, > > ---- > > Anton Vatcky > Senior Software Engineer > Sun Microsystems, Inc. > Level 3, 243 Northbourne Avenue > Lyneham, ACT 2602 Australia > Phone +61 (0)2-6217-5571 > Mobile +61 (0)417-412-628 > Fax +61 (0)2-6257-2664 > Email Anton.Vatcky@Sun.COM > > > > > Thomas Bader wrote: >> Hi all >> >> I have the following tape changer: >> >> server:~# mtx -f /dev/sg0 inquiry >> Product Type: Medium Changer >> Vendor ID: 'STK ' >> Product ID: 'L20 ' >> Revision: '0214' >> Attached Changer API: No >> >> It's a StorageTek L20. It has some tapes in it: >> >> server:~# mtx -f /dev/sg0 status >> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export ) >> Data Transfer Element 0:Empty >> Storage Element 1:Full >> :VolumeTag=000024 Storage Element 2:Empty >> Storage Element 3:Empty >> Storage Element 4:Empty >> Storage Element 5:Empty >> Storage Element 6:Empty >> Storage Element 7:Empty >> Storage Element 8:Empty >> Storage Element 9:Empty >> Storage Element 10:Empty >> Storage Element 11:Full >> :VolumeTag=000023 Storage Element >> 12:Full :VolumeTag=000022 Storage >> Element 13:Full :VolumeTag=000021 >> Storage Element 14:Full Storage Element 15 IMPORT/EXPORT:Empty >> >> Transfering tapes between slots (with mtx transfer) works >> well. Somehow, I'm not able to load all the tapes into the >> drive: >> >> server:~# mtx -f /dev/sg0 load 1 >> Loading media from Storage Element 1 into drive 0... >> mtx: Request Sense: Long Report=yes >> mtx: Request Sense: Valid Residual=no >> mtx: Request Sense: Error Code=70 (Current) >> mtx: Request Sense: Sense Key=Illegal Request >> mtx: Request Sense: FileMark=no >> mtx: Request Sense: EOM=no >> mtx: Request Sense: ILI=no >> mtx: Request Sense: Additional Sense Code = 30 >> mtx: Request Sense: Additional Sense Qualifier = 00 >> mtx: Request Sense: BPV=no >> mtx: Request Sense: Error in CDB=no >> mtx: Request Sense: SKSV=no >> MOVE MEDIUM from Element Address 1000 to 500 Failed >> >> I get the same error for slot 11, 12 and 14 too. Doing the >> same command with slot 14 works fine: >> >> server:~# mtx -f /dev/sg0 load 14 >> Loading media from Storage Element 14 into drive 0...done >> server:~# mtx -f /dev/sg0 status >> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export ) >> Data Transfer Element 0:Full (Storage Element 14 Loaded) >> [...] >> Storage Element 14:Empty >> >> Any idea why I cannot load from the other slots? The >> only difference I encounter between the various slots is >> that 1, 11, 12 and 13 have a VolumeTag while 14 has not. >> >> After having loaded the tape I get some more errors: >> >> server:~# mtx -f /dev/sg0 unload >> Unloading drive 0 into Storage Element 14...Drive needs offline >> before move >> server:~# scsitape -f /dev/st0 offline >> cannot open SCSI device '/dev/st0' - Input/output error >> server:~# mtx -f /dev/sg0 unload >> Unloading drive 0 into Storage Element 14...Drive needs offline >> before move >> server:~# scsitape -f /dev/st0 offline >> cannot open SCSI device '/dev/st0' - Input/output error >> server:~# scsitape -f /dev/st0 rewind >> cannot open SCSI device '/dev/st0' - Input/output error >> server:~# mtx -f /dev/sg0 unload >> Unloading drive 0 into Storage Element 14...done >> server:~# mtx -f /dev/sg0 status >> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export ) >> Data Transfer Element 0:Empty >> [...] >> >> Apparently, I can only do the unload after having invoked 2 >> times offline and one time rewind. >> >> The «cannot open SCSI device» error message appears around >> one or two minutes after I have issued the command. >> According to strace, the process hangs some seconds on the >> following system call: >> >> open("/dev/st0", O_RDWR >> >> While searching the mailing list archives and the FAQ I >> found a hint that with some tape changer models the «random >> mode» should be enabled. I have the user's guide here and it >> doesn't mention anything about a random mode or any tape >> changer mode at all. I also don't see any such configuration >> option in the tape changers menu. >> >> My software versions: >> >> server:~# mtx --version >> mtx version 1.3.11 >> >> I'm running Debian 4.0 with a 2.6.18-5-xen-686 kernel. I >> have build my own Debian package of mtx with the latest >> stable version from the mtx SourceForge download page. I'm >> performing all those commands within a Xen Dom0. >> >> Any ideas how I could solve my problems? I'm not really >> experienced with tape changers, so I'm at a loss. >> >> Regards, Thomas. >> >> ------------------------------------------------------------------------- >> >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >> >> _______________________________________________ >> Mtx-general mailing list >> Mtx...@li... >> https://lists.sourceforge.net/lists/listinfo/mtx-general >> > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > ------------------------------------------------------------------------ > > _______________________________________________ > Mtx-general mailing list > Mtx...@li... > https://lists.sourceforge.net/lists/listinfo/mtx-general > |
|
From: Anton V. <Anton.Vatcky@Sun.COM> - 2008-01-15 23:38:26
Attachments:
anton.vatcky.vcf
|
G'day Robert, We are in agreement about what mtx expects and can do. What I am trying to point out is that the library is capable of supporting different types of media and drives. If the wrong media is request for a drive then it will report the error back to mtx, rather than try to blindly mount it. However, mtx is not able to determine before the mount is request, what type of media is located in a storage element. Other commercial software can interrogate the library to determine the media types available. For this reason I recommend that all media in the library be of the one type and compatible with the drives, so that mtx will not have any issues with hardware incompatibility. Granted that a user should know what media and drives types they have, but in reality most users would not be aware of the compatibility issues with tape drive technology. Regards, ---- Anton Vatcky Senior Software Engineer Sun Microsystems, Inc. Level 3, 243 Northbourne Avenue Lyneham, ACT 2602 Australia Phone +61 (0)2-6217-5571 Mobile +61 (0)417-412-628 Fax +61 (0)2-6257-2664 Email Anton.Vatcky@Sun.COM Robert Nelson wrote: > Anton Vatcky wrote: >> G'day Thomas, >> >> The L20 libraries can support different media type and drive types in >> the one box. However, mtx assumes that only one type of media and >> matching drives is supported. >> >> For mtx to work correctly all media and drives must be of the one >> type in the library. So either DLT or LTO based tape drives and >> media should be used. >> > > What are you basing this on? mtx doesn't know or care what type of > media or drives are installed. It just sends SCSI commands telling > the changer what to do. > >> The L20 library is happy to support both types of media in the one >> box, but mtx has no way of knowing which media belongs with which >> drive. The error message you are receiving seems to indicate this >> incompatibility between the drive and the media. >> > > It is up to the user to know which tapes are compatible with which drives. > >> Another point to consider is ensuring you have cleaning media >> configured and install in the library. This type of media must >> contain a valid tape label starting with CLNxxx, where xxx is any >> number. >> >> At the time that a tape mount is requested, the library will >> determine if the tape drive has indicated it needs cleaning, if this >> is the case, then the library will instead mount a cleaning tape if >> one is installed, wait for the cleaning operation to finish and then >> mount the requested tape into the drive. >> >> This can cause mtx to time-out thinking there is a hardware problem >> as the whole mount operation could take up to 3 minutes to complete. >> For this reason I recommend you specify a longer time-out value for >> mtx to ensure this cleaning operation is take into account. >> >> Also there is a later version of the L20 library firmware revision >> code (0215) that correct a few mounting problems, which may benefit >> you. You can obtain this code at www.support.storagetek.com or >> contact your local Sun Microsystems office to have a technician >> upgrade your system for you. >> >> I hope this help. >> >> Regards, >> >> ---- >> >> Anton Vatcky >> Senior Software Engineer >> Sun Microsystems, Inc. >> Level 3, 243 Northbourne Avenue >> Lyneham, ACT 2602 Australia >> Phone +61 (0)2-6217-5571 >> Mobile +61 (0)417-412-628 >> Fax +61 (0)2-6257-2664 >> Email Anton.Vatcky@Sun.COM >> >> >> >> >> Thomas Bader wrote: >>> Hi all >>> >>> I have the following tape changer: >>> >>> server:~# mtx -f /dev/sg0 inquiry >>> Product Type: Medium Changer >>> Vendor ID: 'STK ' >>> Product ID: 'L20 ' >>> Revision: '0214' >>> Attached Changer API: No >>> >>> It's a StorageTek L20. It has some tapes in it: >>> >>> server:~# mtx -f /dev/sg0 status >>> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export ) >>> Data Transfer Element 0:Empty >>> Storage Element 1:Full >>> :VolumeTag=000024 Storage Element >>> 2:Empty >>> Storage Element 3:Empty >>> Storage Element 4:Empty >>> Storage Element 5:Empty >>> Storage Element 6:Empty >>> Storage Element 7:Empty >>> Storage Element 8:Empty >>> Storage Element 9:Empty >>> Storage Element 10:Empty >>> Storage Element 11:Full >>> :VolumeTag=000023 Storage Element >>> 12:Full :VolumeTag=000022 Storage >>> Element 13:Full :VolumeTag=000021 >>> Storage Element 14:Full Storage Element 15 IMPORT/EXPORT:Empty >>> >>> Transfering tapes between slots (with mtx transfer) works >>> well. Somehow, I'm not able to load all the tapes into the >>> drive: >>> >>> server:~# mtx -f /dev/sg0 load 1 >>> Loading media from Storage Element 1 into drive 0... >>> mtx: Request Sense: Long Report=yes >>> mtx: Request Sense: Valid Residual=no >>> mtx: Request Sense: Error Code=70 (Current) >>> mtx: Request Sense: Sense Key=Illegal Request >>> mtx: Request Sense: FileMark=no >>> mtx: Request Sense: EOM=no >>> mtx: Request Sense: ILI=no >>> mtx: Request Sense: Additional Sense Code = 30 >>> mtx: Request Sense: Additional Sense Qualifier = 00 >>> mtx: Request Sense: BPV=no >>> mtx: Request Sense: Error in CDB=no >>> mtx: Request Sense: SKSV=no >>> MOVE MEDIUM from Element Address 1000 to 500 Failed >>> >>> I get the same error for slot 11, 12 and 14 too. Doing the >>> same command with slot 14 works fine: >>> >>> server:~# mtx -f /dev/sg0 load 14 >>> Loading media from Storage Element 14 into drive 0...done >>> server:~# mtx -f /dev/sg0 status >>> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export ) >>> Data Transfer Element 0:Full (Storage Element 14 Loaded) >>> [...] >>> Storage Element 14:Empty >>> >>> Any idea why I cannot load from the other slots? The >>> only difference I encounter between the various slots is >>> that 1, 11, 12 and 13 have a VolumeTag while 14 has not. >>> >>> After having loaded the tape I get some more errors: >>> >>> server:~# mtx -f /dev/sg0 unload >>> Unloading drive 0 into Storage Element 14...Drive needs offline >>> before move >>> server:~# scsitape -f /dev/st0 offline >>> cannot open SCSI device '/dev/st0' - Input/output error >>> server:~# mtx -f /dev/sg0 unload >>> Unloading drive 0 into Storage Element 14...Drive needs offline >>> before move >>> server:~# scsitape -f /dev/st0 offline >>> cannot open SCSI device '/dev/st0' - Input/output error >>> server:~# scsitape -f /dev/st0 rewind >>> cannot open SCSI device '/dev/st0' - Input/output error >>> server:~# mtx -f /dev/sg0 unload >>> Unloading drive 0 into Storage Element 14...done >>> server:~# mtx -f /dev/sg0 status >>> Storage Changer /dev/sg0:1 Drives, 15 Slots ( 1 Import/Export ) >>> Data Transfer Element 0:Empty >>> [...] >>> >>> Apparently, I can only do the unload after having invoked 2 >>> times offline and one time rewind. >>> >>> The «cannot open SCSI device» error message appears around >>> one or two minutes after I have issued the command. >>> According to strace, the process hangs some seconds on the >>> following system call: >>> >>> open("/dev/st0", O_RDWR >>> >>> While searching the mailing list archives and the FAQ I >>> found a hint that with some tape changer models the «random >>> mode» should be enabled. I have the user's guide here and it >>> doesn't mention anything about a random mode or any tape >>> changer mode at all. I also don't see any such configuration >>> option in the tape changers menu. >>> >>> My software versions: >>> >>> server:~# mtx --version >>> mtx version 1.3.11 >>> >>> I'm running Debian 4.0 with a 2.6.18-5-xen-686 kernel. I >>> have build my own Debian package of mtx with the latest >>> stable version from the mtx SourceForge download page. I'm >>> performing all those commands within a Xen Dom0. >>> >>> Any ideas how I could solve my problems? I'm not really >>> experienced with tape changers, so I'm at a loss. >>> >>> Regards, Thomas. >>> >>> ------------------------------------------------------------------------- >>> >>> Check out the new SourceForge.net Marketplace. >>> It's the best place to buy or sell services for >>> just about anything Open Source. >>> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >>> >>> _______________________________________________ >>> Mtx-general mailing list >>> Mtx...@li... >>> https://lists.sourceforge.net/lists/listinfo/mtx-general >>> >> ------------------------------------------------------------------------- >> Check out the new SourceForge.net Marketplace. >> It's the best place to buy or sell services for >> just about anything Open Source. >> http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> Mtx-general mailing list >> Mtx...@li... >> https://lists.sourceforge.net/lists/listinfo/mtx-general >> > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace > > ------------------------------------------------------------------------ > > _______________________________________________ > Mtx-general mailing list > Mtx...@li... > https://lists.sourceforge.net/lists/listinfo/mtx-general > |
|
From: Thomas B. <th...@tr...> - 2008-01-24 20:24:14
|
Hello all of you Thank you for the hints about wrong media type. Anton Vatcky schrieb: > For mtx to work correctly all media and drives must be of the one type > in the library. So either DLT or LTO based tape drives and media should > be used. This was exactly the problem. I replaced all tapes and now I could at least load/unload and read/write two of the tapes. That's already a bit of success. However, there's another problem: We installed 19 tapes into the tape library. But mtx only sees 14 tape slots, while we have 19 (for example in the mtx status output). Any ideas what could be wrong now? Regards, Thomas. |
|
From: Wes B. <ws...@pa...> - 2008-01-24 22:37:39
|
Some loaders can configure the number of slots to use. Assuming this loader has a front panel to configure it, look for options to change the number of slots in use. Wes Thomas Bader wrote: > Hello all of you > > Thank you for the hints about wrong media type. > > Anton Vatcky schrieb: > >>For mtx to work correctly all media and drives must be of the one type >>in the library. So either DLT or LTO based tape drives and media should >>be used. > > > This was exactly the problem. I replaced all tapes and now I could at > least load/unload and read/write two of the tapes. That's already a bit > of success. > > However, there's another problem: We installed 19 tapes into the tape > library. But mtx only sees 14 tape slots, while we have 19 (for example > in the mtx status output). Any ideas what could be wrong now? > > Regards, Thomas. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Mtx-general mailing list > Mtx...@li... > https://lists.sourceforge.net/lists/listinfo/mtx-general > > |
Thanks for helping keep SourceForge clean.
X