mtx-general Mailing List for MTX: Media Changer Tools
Brought to you by:
elgreen,
robertnelson
Menu
▾
▴
mtx-general — General Discussion
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(5) |
Jun
(76) |
Jul
(91) |
Aug
(21) |
Sep
(36) |
Oct
(21) |
Nov
(27) |
Dec
(40) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(27) |
Feb
(27) |
Mar
(30) |
Apr
(82) |
May
(50) |
Jun
(34) |
Jul
(1) |
Aug
(12) |
Sep
(6) |
Oct
(11) |
Nov
(8) |
Dec
(17) |
| 2002 |
Jan
(59) |
Feb
(23) |
Mar
(11) |
Apr
(30) |
May
(19) |
Jun
(13) |
Jul
(25) |
Aug
(7) |
Sep
(23) |
Oct
(33) |
Nov
(18) |
Dec
(5) |
| 2003 |
Jan
(7) |
Feb
(51) |
Mar
(30) |
Apr
(16) |
May
(1) |
Jun
(25) |
Jul
(23) |
Aug
(18) |
Sep
(10) |
Oct
(4) |
Nov
(11) |
Dec
(4) |
| 2004 |
Jan
(1) |
Feb
(23) |
Mar
(47) |
Apr
(15) |
May
(8) |
Jun
(2) |
Jul
(1) |
Aug
(16) |
Sep
(7) |
Oct
(4) |
Nov
(3) |
Dec
(1) |
| 2005 |
Jan
(6) |
Feb
|
Mar
(5) |
Apr
(10) |
May
(27) |
Jun
(26) |
Jul
(1) |
Aug
(4) |
Sep
|
Oct
(1) |
Nov
(8) |
Dec
(7) |
| 2006 |
Jan
(10) |
Feb
(6) |
Mar
(8) |
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(5) |
Sep
(6) |
Oct
(1) |
Nov
(6) |
Dec
(13) |
| 2007 |
Jan
(40) |
Feb
(44) |
Mar
(21) |
Apr
(15) |
May
(7) |
Jun
(7) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
|
Nov
(12) |
Dec
|
| 2008 |
Jan
(12) |
Feb
(5) |
Mar
|
Apr
(3) |
May
|
Jun
(1) |
Jul
(2) |
Aug
(11) |
Sep
(1) |
Oct
(1) |
Nov
|
Dec
|
| 2009 |
Jan
(8) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
(4) |
Sep
(2) |
Oct
|
Nov
(5) |
Dec
(1) |
| 2010 |
Jan
(12) |
Feb
|
Mar
(4) |
Apr
|
May
(3) |
Jun
(4) |
Jul
(7) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(6) |
| 2011 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
(7) |
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(2) |
Dec
(1) |
| 2012 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(3) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
|
From: David N. <Dj...@li...> - 2022-11-04 15:07:07
|
Hello,
I have been using the 'mtx' command- under Rocky Linux -to control an IBM 3573-TL
Tape Library with two LTO SAS drive modules installed.
The Linux. 'lsscsi' command shows the mt & generic drivers' devices as follows:
[1:0:1:0] tape IBM ULT3580-HH8 N4Q1 /dev/st1 /dev/sg4
[1:0:1:1] mediumx IBM 3573-TL 1500 /dev/sch1 /dev/sg5
[1:0:3:0] tape IBM ULT3580-HH6 KAJ9 /dev/st0 /dev/sg1
However 'mtx' only reports one data transport element - the one corresponding to the
LTO-6 drive:
[root@bg-fs2 ~]#
[root@bg-fs2 ~]#
[root@bg-fs2 ~]# mtx.debug status |head -20
0000: 17 00 00 00 9D 12 00 00 00 01 03 E9 00 23 00 65 '.............#.e'
0010: 00 05 00 01 00 01 00 00 20 20 20 20 20 20 '........ '
*sense_page=9d 9d
rawNumStorage= 0 35 rawNumImportExport= 0 5
rawNumTransport=0 1 rawNumDataTransfer=0 1
NumMediumTransport=1
NumStorage=40
NumImportExport=5
NumDataTransfer=1
MaxReadElementStatusData=3568
NumElements=42
Storage Changer /dev/sg5:1 Drives, 40 Slots ( 5 Import/Export )
Data Transfer Element 0:Empty
Storage Element 1:Empty
Storage Element 2:Empty
Storage Element 3:Empty
Storage Element 4:Empty
Storage Element 5:Empty
From looking at the above dump of the input buffer (and the source code) I think
'mtx' is correctly reporting on the information it has been given.
If I can obtain a SCSI manual for this libary what codes/settings should I be
checking ?
Thanks in advance for any insights.
|
|
From: James Y. <ja...@yo...> - 2021-05-30 08:50:54
|
It seems to me that (if I'm looking in the right place) the SVN repo was last updated in 2009. Is this still the canonical home of this package? Has the project been forked (and is more active elsewhere)? Thanks, James. |
|
From: James Y. <ja...@yo...> - 2021-05-30 08:47:16
|
This patch includes three types of changes: 1. Suggest "lscsi" instead of "cat /proc/scsi/scsi" for Linux, because the latter has been a legacy feature since about 2011. 2. Update Linux device file naming to match usual names with udev. 3. Mention some more modern tape hardware on which the tools have been tested. These changes span a number of manpages and the FAQ. Some parts of the diff also remove trailing blanks from the documentation files. James. |
|
From: Christian S. <chr...@cm...> - 2021-04-21 10:25:59
|
Good day, I have tried to figure out how to eject the I/O station using mtx or other Linux commands. >From the SCSI reference for TS3200 I can see the command "OPEN/CLOSE IMPORT/EXPORT ELEMENT". References: http://ps-2.kev009.com/rs6000/manuals/Tape/TS3100_TS3200/IBM_System_Storage_TS3100_Tape_Library_and_TS3200_Tape_Library_SCSI_Reference_GA32-0547-01.pdf https://www.t10.org/ftp/t10/document.05/05-070r3.pdf Is it possible to control the I/O station today, or if not - is that something that would be a welcome addition? Regards, |
|
From: Heitor F. <he...@ba...> - 2018-05-04 18:21:43
|
Dear List, I'm new here. I hope there is someone alive. I was always intrigued by the fact there is no easy way of determining Linux Tape-Library drives order, as displayed by mtx status command (Ref: https://sourceforge.net/p/mtx/mailman/message/6018053/), that says the only way to really make sure about the drives order is to insert tapes into each drive. Since mtx is always capable of determining the correct order of the drives, is it possible to also inform any /dev/sg*, /dev/nst* or /dev/tape/by-id/* device path association? Maybe if the user set a special command option? Regards, -- Heitor Medrado de Faria | EB-1 Visa | LPIC-III | ITIL-F | EMC 05-001 • Check my Bacula Book at Amazon.com http://bacula.us/book • Do you need Bacula training? http://bacula.us/video-classes/ • USA +1 (323) 300-5387 | Brazil +55 (61) 98268-4220 | http://bacula.us |
|
From: Andy S. <and...@gm...> - 2018-02-23 22:38:46
|
Hello mtx fans, I recently procured an Exabyte VXA-2 PacketLoader with a Firewire interface. I have used mtx many times with LVD-SCSI, but Firewire is proving troublesome. In particular, my Linux kernel is only finding one device (EITHER the tape drive or the robot), but not both. And whichever one is found varies across reboots! However, I do see in my dmesg log that both devices are recognized, but with different LUNs (instead of different SCSI IDs as I normally see with LVD-SCSI). Has anybody successfully figured out this autoloader? Given the SCSI and Firewire rewrites over the recent years, it is hard to find up-to-date documentation on this stuff. I am using Debian 9 (kernel 3.16.0) with the firewire_sbp2 module. Regards, --Andy Stevens Port Chester, NY |
|
From: David S. <da...@re...> - 2016-01-13 23:25:34
|
Hi,
We have received a bug report and patch from Wayne Keseberg (EMC)
against mtx-1.3.12 that it will fail if it is run against a storage unit
with more than 25.000 slots. This will fail both against real libraries
butis just as easy to create using virtual libraries.
Steps to Reproduce:
1. create a virtual library (FC device) with 30,000 slots
2. find sg device with command such as "lsscsi -g"
3. issue "mtx -f /dev/sgX status"
Actual results:
[root@wknow wayne]# mtx -f /dev/sg4 status
mtx: Request Sense: Long Report=yes
mtx: Request Sense: Valid Residual=no
mtx: Request Sense: Error Code=0 (Unknown?!)
mtx: Request Sense: Sense Key=No Sense
mtx: Request Sense: FileMark=no
mtx: Request Sense: EOM=no
mtx: Request Sense: ILI=no
mtx: Request Sense: Additional Sense Code = 00
mtx: Request Sense: Additional Sense Qualifier = 00
mtx: Request Sense: BPV=no
mtx: Request Sense: Error in CDB=no
mtx: Request Sense: SKSV=no
READ ELEMENT STATUS Command Failed
[root@wknow wayne]#
More details on the patch from the Wayne:
----------------------------------------------------------
Here is an outline of the changes that make mtx work. One of the
issues is there is no equivalent of SCSI command Read Block Limits for
library devices as there is for tape so how do you know the maximum
byte count? To get around this, backup applications issue Read Element
Status for small element counts, bumping up the starting element in a
loop until information for all elements (data storage elements, really,
that is slots since that type of element that will number in the
thousands..) have been read. Backup Exec, for example, obtains Read
Element Status for 32 elements at a time.
The necessary changes are only in mtxl.c
Add a definition for the number of elements to be read in one go:
/* only so many element per SCSI Read Element Status */
#define SCSI_RES_ELEMENTS 10000
In routine ReadElementStatus(), add a few variables
int FirstElem, NumElements, NumThisRES;
While processing STORAGE ELEMENTS, add a do statement before calling
SendElementStatusRequest() that executes all the code for STORAGE
ELEMENTS and initialize the new variables
NumElements = mode_sense->NumStorage - mode_sense->NumImportExport;
FirstElem = mode_sense->StorageStart;
do
{
NumThisRES = (NumElements > SCSI_RES_ELEMENTS ? SCSI_RES_ELEMENTS : NumElements);
Change the arguments to SendElementStatusRequest() to reflect just the
number of elements being requested (NumThisREM) and byte count
(SCSI_RES_ELEMENTS * 52 +120).
Before the end of the new do statement adjust variable for the next
iteration
FirstElem += SCSI_RES_ELEMENTS;
NumElem -= SCSI_RES_ELEMENTS;
And then for the other element types (IMPORT/EXPORT, DRIVES, and Robot
arm(s)) change the byte count requested to
SCSI_RES_ELEMENTS * 52 +120. This will not present a problems since
SCSI_RES_ELEMENTS at 10,000 is more than sufficient for all IE or data
transfer or medium transfer element counts of libraries whether real or
virtual.
----------------------------------------------------------
The attached patch is slightly modified by me, to make the contribution
adhere to the current coding style in mtxl.c. I've also done a changes
in regards to make the patch set less intrusive. The functionality of
the patch has not been changed.
One difference I noticed is that the patch uses 5.000 for
SCSI_RES_ELEMENTS instead of 10.000 as the bug comment says. I do not
know yet if that have any real impact on the functionality.
Is this something you would consider to include into mtx?
--
kind regards,
David Sommerseth
|
|
From: Michael M. <ml...@ad...> - 2016-01-04 17:24:14
|
On 01/04/2016 06:52 AM, Andy Cress wrote: > > Changer: IBM 3573-TL > > Tape device: IBM ULT3580-HH6 > > Somehow this guy managed to apply tape labels with the most > significant part after the first 8 characters, which obviously caused > problems. > > # mtx -f /dev/sg5 status > > Storage Changer /dev/sg5:1 Drives, 23 Slots ( 0 Import/Export ) > > Data Transfer Element 0:Empty > > Storage Element 1:Full :VolumeTag=LTO11063 > > Storage Element 2:Full :VolumeTag=LTO11063 > > Storage Element 3:Full :VolumeTag=LTO11063 > > Storage Element 4:Full :VolumeTag=LTO11063 > > Storage Element 5:Empty > > Storage Element 6:Empty > > We had him relabel the tapes, deleting the first 3 characters and all > is well, but this raises the question: > > Is there a defined limit on the length of the tape labels? I have > never seen one longer than 8 characters, and mtx did not read the > additional characters beyond 8. Or could it be that when the label > got written, it truncated to 8 characters? > > Andy > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Mtx-general mailing list > Mtx...@li... > https://lists.sourceforge.net/lists/listinfo/mtx-general Look to see if your tape machine has a setting to report 'extended barcodes.' |
|
From: Andy C. <ac...@un...> - 2016-01-04 16:26:30
|
Changer: IBM 3573-TL Tape device: IBM ULT3580-HH6 Somehow this guy managed to apply tape labels with the most significant part after the first 8 characters, which obviously caused problems. # mtx -f /dev/sg5 status Storage Changer /dev/sg5:1 Drives, 23 Slots ( 0 Import/Export ) Data Transfer Element 0:Empty Storage Element 1:Full :VolumeTag=LTO11063 Storage Element 2:Full :VolumeTag=LTO11063 Storage Element 3:Full :VolumeTag=LTO11063 Storage Element 4:Full :VolumeTag=LTO11063 Storage Element 5:Empty Storage Element 6:Empty We had him relabel the tapes, deleting the first 3 characters and all is well, but this raises the question: Is there a defined limit on the length of the tape labels? I have never seen one longer than 8 characters, and mtx did not read the additional characters beyond 8. Or could it be that when the label got written, it truncated to 8 characters? Andy |
|
From: Thibault <thi...@ca...> - 2015-08-28 09:25:11
|
Thank you very much ! I found this setting on my library tape configuration menu (Standard to Plus Six fixed the problem). Regards, Thibault Leboucq -----Message d'origine----- De : Michael Morrison [mailto:ml...@ad...] Envoyé : vendredi 28 août 2015 02:47 À : mtx...@li... Objet : Re: [Mtx-general] Wrong barcode read On 08/27/2015 01:40 AM, Thibault wrote: > > Hi, > > Any idea why my system (CENTOS 6.5) doesn’t see my barcode correctly > with MTX ? > > If I put a tape T00001L5 then mtx –f /dev/sgx status show me T00001. > > I’ve checked on the web access of my library tape and it is correctly > reading the barcode on his side T00001L5. > > It seems to be a problem with mtx. > > Thanks > > Thibault Leboucq > > > > ---------------------------------------------------------------------- > -------- > > > _______________________________________________ > Mtx-general mailing list > Mtx...@li... > https://lists.sourceforge.net/lists/listinfo/mtx-general Look to see if your tape machine has a setting to report 'extended barcodes.' Had a similar problem, but was many many years ago..... ------------------------------------------------------------------------------ _______________________________________________ Mtx-general mailing list Mtx...@li... https://lists.sourceforge.net/lists/listinfo/mtx-general |
|
From: Michael M. <ml...@ad...> - 2015-08-28 01:02:33
|
On 08/27/2015 01:40 AM, Thibault wrote: > > Hi, > > Any idea why my system (CENTOS 6.5) doesn’t see my barcode correctly > with MTX ? > > If I put a tape T00001L5 then mtx –f /dev/sgx status show me T00001. > > I’ve checked on the web access of my library tape and it is correctly > reading the barcode on his side T00001L5. > > It seems to be a problem with mtx. > > Thanks > > Thibault Leboucq > > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > Mtx-general mailing list > Mtx...@li... > https://lists.sourceforge.net/lists/listinfo/mtx-general Look to see if your tape machine has a setting to report 'extended barcodes.' Had a similar problem, but was many many years ago..... |
|
From: Thibault <thi...@ca...> - 2015-08-27 08:41:02
|
Hi, Any idea why my system (CENTOS 6.5) doesn't see my barcode correctly with MTX ? If I put a tape T00001L5 then mtx -f /dev/sgx status show me T00001. I've checked on the web access of my library tape and it is correctly reading the barcode on his side T00001L5. It seems to be a problem with mtx. Thanks Thibault Leboucq |
|
From: Georgy F. <gfe...@un...> - 2015-02-27 11:30:41
|
Hi All, Where do we get the latest source for the MTX utility ? E.g. there is a patch submitted to Debian Sid : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728142 -- see message #10 , But I see the latest code update at http://sourceforge.net/p/mtx/code/HEAD/tree/ happened in 2009 . Is this patch going to be approved or discarded ? The reason I'm asking is that I'd like to make some custom changes to the code, which are probably not worth sharing ( unless you're interested ), but would also like to do a few amendments along the way ( e.g. "sprintf(TargetPointer,"%s: ",argv0);" line at "mtxl.c:175" probably makes no effect for any non-empty ErrorMessage string ) . So I wonder what code repository should I refer to, how do I commit patches, etc. Best regards, George -- George Fedorov Senior Systems Specialist Melbourne School of Engineering The University of Melbourne, Victoria 3010, Australia http://www.eng.unimelb.edu.au/ |
|
From: Ellison M. <em...@sc...> - 2015-02-13 00:15:18
|
On 2/6/2015 9:53 PM, Eric Green wrote: > Is it possible to put the text of the kernel panic here? > > mtx just puts standard SCSI CDB's to a standard API. It is possible > that an API changed inside the kernel but the more likely explanation > is a driver issue where it is assuming it's a SAS2 CDB and accessing > fields that don't exist in a SAS1/SCSI CDB. > > Also helpful would be to know what version of the kernel you are running: > > cat /proc/version > > That will allow me to get the correct kernel source ball to match with > the exception stack trace. > >> On Feb 6, 2015, at 17:49, Ellison Marks <em...@sc... >> <mailto:em...@sc...>> wrote: >> >> Hello, >> >> While I realize this list isn't too active anymore, I hope someone may >> have some insight about an issue I'm encountering. >> >> OS: CentOS 6 >> Tape Library: Dell PowerVault TL2000/IBM 3573-TL >> Adapter: PERC 5/E SAS >> mtx version: mtx-1.3.12-5.el6.x86_64 >> >> The tape library shows up as /dev/sg2, and the inquiry and status >> commands work fine. Trying to get it to load or unload a tape, however, >> causes a kernel panic, apparently somewhere in the scsi drivers. The >> tape is still loaded or unloaded as requested, visible when the machine >> is restarted. >> >> May be related to http://sourceforge.net/p/mtx/feature-requests/10/ >> >> Any help would be appreciated. >> >> -- >> Sincerely, >> Ellison >> >> Ellison Marks >> Scratchspace Inc. >> (831) 621-7928 >> http://www.scratchspace.com >> >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming. The Go Parallel Website, >> sponsored by Intel and developed in partnership with Slashdot Media, >> is your >> hub for all things parallel software development, from weekly thought >> leadership blogs to news, videos, case studies, tutorials and more. >> Take a >> look and join the conversation now. http://goparallel.sourceforge.net/ >> _______________________________________________ >> Mtx-general mailing list >> Mtx...@li... >> https://lists.sourceforge.net/lists/listinfo/mtx-general > > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now.http://goparallel.sourceforge.net/ > > > _______________________________________________ > Mtx-general mailing list > Mtx...@li... > https://lists.sourceforge.net/lists/listinfo/mtx-general (resent, as I attached the picture to the previous message, making it to large) Unfortunately I don't think we can get the full panic at the moment. We did get a picture of the console (http://i.imgur.com/mqBG1dJ.jpg), but some of the output was lost in the scrollback. Kernel version is currently the latest from CentOS. # rpm -q kernel kernel-2.6.32-504.8.1.el6.x86_64 # cat /proc/version Linux version 2.6.32-504.8.1.el6.x86_64 (moc...@c6...) (gcc version 4.4.7 20120313 (Red Hat 4.4.7-11) (GCC) ) #1 SMP Wed Jan 28 21:11:36 UTC 2015 -- Sincerely, Ellison Ellison Marks Scratchspace Inc. (831) 621-7928 http://www.scratchspace.com |
,){kind=link}
|
From: Eric G. <er...@ba...> - 2015-02-07 05:53:30
|
Is it possible to put the text of the kernel panic here? mtx just puts standard SCSI CDB's to a standard API. It is possible that an API changed inside the kernel but the more likely explanation is a driver issue where it is assuming it's a SAS2 CDB and accessing fields that don't exist in a SAS1/SCSI CDB. Also helpful would be to know what version of the kernel you are running: cat /proc/version That will allow me to get the correct kernel source ball to match with the exception stack trace. > On Feb 6, 2015, at 17:49, Ellison Marks <em...@sc...> wrote: > > Hello, > > While I realize this list isn't too active anymore, I hope someone may > have some insight about an issue I'm encountering. > > OS: CentOS 6 > Tape Library: Dell PowerVault TL2000/IBM 3573-TL > Adapter: PERC 5/E SAS > mtx version: mtx-1.3.12-5.el6.x86_64 > > The tape library shows up as /dev/sg2, and the inquiry and status > commands work fine. Trying to get it to load or unload a tape, however, > causes a kernel panic, apparently somewhere in the scsi drivers. The > tape is still loaded or unloaded as requested, visible when the machine > is restarted. > > May be related to http://sourceforge.net/p/mtx/feature-requests/10/ > > Any help would be appreciated. > > -- > Sincerely, > Ellison > > Ellison Marks > Scratchspace Inc. > (831) 621-7928 > http://www.scratchspace.com > > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming. The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Mtx-general mailing list > Mtx...@li... > https://lists.sourceforge.net/lists/listinfo/mtx-general |
|
From: Mr. J. W. L. <ba...@ba...> - 2015-02-07 02:55:16
|
Hello Ellison , On Fri, 6 Feb 2015, Ellison Marks wrote: > Hello, > > While I realize this list isn't too active anymore, I hope someone may > have some insight about an issue I'm encountering. > > OS: CentOS 6 > Tape Library: Dell PowerVault TL2000/IBM 3573-TL > Adapter: PERC 5/E SAS Is there only one tape drive ? And is it the only item on this controller ? You are aware that this contoller is specifically for 'Raid' applications ? Or have you reflashed it to be a JBD controller ? > mtx version: mtx-1.3.12-5.el6.x86_64 > > The tape library shows up as /dev/sg2, and the inquiry and status > commands work fine. Trying to get it to load or unload a tape, however, > causes a kernel panic, apparently somewhere in the scsi drivers. The > tape is still loaded or unloaded as requested, visible when the machine > is restarted. If my memory serves correctly there is(was) a change in the scsi command set for SAS base devices . Can you post some place the full dmesg output of the panic ? And here the full output from 'mtx status /dev/sg2' and 'mtx inquiry' ? > May be related to http://sourceforge.net/p/mtx/feature-requests/10/ The above location is (IMO) not a very good place to put help requests . I hope the gentle person got some help with the difficulty from someone . Yes it sounds sort of similar tho th eHang isn't what you are experiencing . > Any help would be appreciated. Hth , JimL -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | ba...@ba... | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+ |
|
From: Ellison M. <em...@sc...> - 2015-02-07 01:49:35
|
Hello, While I realize this list isn't too active anymore, I hope someone may have some insight about an issue I'm encountering. OS: CentOS 6 Tape Library: Dell PowerVault TL2000/IBM 3573-TL Adapter: PERC 5/E SAS mtx version: mtx-1.3.12-5.el6.x86_64 The tape library shows up as /dev/sg2, and the inquiry and status commands work fine. Trying to get it to load or unload a tape, however, causes a kernel panic, apparently somewhere in the scsi drivers. The tape is still loaded or unloaded as requested, visible when the machine is restarted. May be related to http://sourceforge.net/p/mtx/feature-requests/10/ Any help would be appreciated. -- Sincerely, Ellison Ellison Marks Scratchspace Inc. (831) 621-7928 http://www.scratchspace.com |
|
From: Guillermo L. <gle...@op...> - 2011-12-13 17:42:04
|
Hello Folks, I have two drives SDLT600 with tapes SDLT of 320GB in the library HP MSL6052, but no is possible write in them (for output of tapeinfo command show below). The write protect switch in the cartridges is disable. ¿what can be write proctect the tapes?. Thanks. # tapeinfo -f /dev/sg6 Product Type: Tape Drive Vendor ID: 'HP ' Product ID: 'SDLT600 ' Revision: '2929' Attached Changer API: No SerialNumber: 'MYK0830KS2 ' MinBlock: 4 MaxBlock: 16777212 SCSI ID: 0 SCSI LUN: 2 Ready: yes WriteProtect: yes BufferedMode: yes Medium Type: 0x86 Density Code: 0x49 BlockSize: 0 DataCompEnabled: yes DataCompCapable: yes DataDeCompEnabled: yes CompType: 0x10 DeCompType: 0x10 BOP: yes Block Position: 0 ActivePartition: 0 EarlyWarningSize: 0 NumPartitions: 0 MaxPartitions: 0 |
|
From: Gerhardus G. <ger...@gm...> - 2011-11-29 15:13:45
|
Hi I get an error when trying to load a tape: mtx load 114 3 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=yes mtx: Request Sense: SKSV=no MOVE MEDIUM from Element Address 1113 to 503 Failed I think the problem is with the tape but not sure why.... I say that because I can load other tapes into the same drive with no problem. When I unload other tapes and try to load this tape it gives me the error above. Currently my next course of action is to reset the tape robot but that is a bit drastic and I am not sure it will solve the problem but I am trying. The tape robot is a SL500 StorageTek and I am using RHEL 5.5 and the rpm version of mtx is: 1.2.18-9 Regards -- Gerhardus Geldenhuis |
|
From: Bodo B. <B....@bk...> - 2011-10-23 17:21:05
|
Hi there, I was wondering, if there is a generic driver for SAS (Serial attached SCSI) like gsc available. I have a HP 1/8 G2 Autoloader Ultrium 920 SAS connected to an IBM P710 running AIX 5.3. I am unable to get gsc up an running. Is there anybody out there who has some ideas about using mtx in such a configuration? Thank you very much in advance for your help! Best regards Bodo -- b+k CAD/CAM Unternehmensberatung GmbH Daimlerstr. 1 38112 Braunschweig http://www.bk-cad.de |
|
From: Mr. J. W. L. <ba...@ba...> - 2011-08-05 18:05:49
|
Hello Alden , On Fri, 5 Aug 2011, Alden Timme wrote: > Hi again, > > Thank you for the help. Sorry for the delay - we tried a new controller > (Adaptec 2260300-R 2045 RAID), but unfortunately now the controller only > sees our tape library as a tape drive, but not a changer: You need to set 'CONFIG_SCSI_MULTI_LUN' to yes in the kernel config & rebuild . Also make sure that the controller is set to report all LUN's . There appears NOT to be a way using 'sysctl' or any other method I can find from the CLI . Hth , JimL > $ lsscsi -g > [0:0:0:0] cd/dvd HL-DT-ST CDRW/DVD GCC4244 B101 /dev/sr0 /dev/sg0 > [2:0:32:0] enclosu DP BACKPLANE 1.05 - /dev/sg1 > [2:2:0:0] disk DELL PERC 6/i 1.22 /dev/sda > /dev/sg2[3:3:0:0] tape IBM ULT3580-HH4 97F1 /dev/st0 > /dev/sg3 > > > $ cat /proc/scsi/scsi > Attached devices: > Host: scsi0 Channel: 00 Id: 00 Lun: 00 > Vendor: HL-DT-ST Model: CDRW/DVD GCC4244 Rev: B101 > Type: CD-ROM ANSI SCSI revision: 05 > Host: scsi2 Channel: 00 Id: 32 Lun: 00 > Vendor: DP Model: BACKPLANE Rev: 1.05 > Type: Enclosure ANSI SCSI revision: 05 > Host: scsi2 Channel: 02 Id: 00 Lun: 00 > Vendor: DELL Model: PERC 6/i Rev: 1.22 > Type: Direct-Access ANSI SCSI revision: 05 > Host: scsi3 Channel: 03 Id: 00 Lun: 00 > Vendor: IBM Model: ULT3580-HH4 Rev: 97F1 > Type: Sequential-Access ANSI SCSI revision: 03 > > > although now mt -f /dev/nst0 eject works, without the Input/Output error > from before (after I've loaded a tape from the Dell web interface): > > $ mt -f /dev/nst0 status > SCSI 2 tape drive: > File number=0, block number=0, partition=0. > Tape block size 0 bytes. Density code 0x46 (LTO-4). > Soft error count since last status=0 > General status bits on (41010000): > BOT ONLINE IM_REP_EN > > $ mt -f /dev/nst0 eject > $ echo $? > 0 > > Is this just an incompatible raid controller? If so, then maybe to take a > step back, has anyone found a good raid controller that will work with mtx > for a Dell PowerEdge 2950 and a Dell TL 4000? This must be a fairly common > combination... > > Thanks in advance! > > Alden > > On Mon, Jul 25, 2011 at 11:11 AM, Mr. James W. Laferriere < > ba...@ba...> wrote: > >> Hello Alden , >> >> On Mon, 25 Jul 2011, Alden Timme wrote: >>> Thanks for the continued help! Unfortunately, I still can't get it to >>> work... >>> >>> I looked through the MTX FAQ (also here: >> http://mtx.sourceforge.net/faq.html), >>> and went through some of their suggestions for problems that looked >> similar >>> to mine (in III. Operational issues): >>> - my mtx is not busted (this was happening on the Ubuntu native package >>> version 1.3.12 and still on version 2.0.0 from svn) >>> - my loader is in Random mode. I even switched it to Sequential to try it >>> out and then back - no luck. I can't even get mtx status to work when in >>> sequential mode, although I don't know if that is expected. >>> - I tried each of mt {offline | rewoffl | eject}, and each time got the >>> following error: >>> >>> $ mt -f /dev/nst0 eject >>> /dev/nst0: Input/output error >>> >>> even though that is the path to the tape device: >>> >>> $ lsscsi -g >>> [0:0:0:0] cd/dvd HL-DT-ST CDRW/DVD GCC4244 B101 /dev/sr0 /dev/sg0 >>> [2:0:32:0] enclosu DP BACKPLANE 1.05 - /dev/sg1 >>> [2:2:0:0] disk DELL PERC 6/i 1.22 /dev/sda /dev/sg2 >>> [3:0:48:0] tape IBM ULT3580-HH4 97F1 /dev/st0 /dev/sg3 >>> [3:0:48:1] mediumx IBM 3573-TL 8.40 /dev/sch0 /dev/sg4 >> >> I hope that (at worst) the Perc6/i is in 'Just a bunch of disks' >> mode . >> Even a that most 'Raid capable' controllers have fits when attaching >> tape drives to them . >> Try finding a plain scsi controller to attach the tape robot to & >> use >> that . Much less difficulties when going that route . >> The clincher is that 'mt' doesn't seem to find the tape drive either >> . >> >> Hth , JimL >> >>> One (perhaps) interesting thing is that mt -f /dev/nst0 {offline | >> rewoffle >>> | eject} takes a little while to show the error, and while I am waiting >> for >>> the mt command, I can see the drive status move from "Closed" to >> "Unloading" >>> and then back to "Closed" (without actually unloading). >>> N.B. This is from the web/gui interface for the changer, which comes with >> it >>> as a Dell product. >>> Also note that I was wrong (from my first post) about mt -f /dev/nst0 >>> actually unloading the tape... >>> >>> Also, FYI I don't ever see any errors when loading/unloading using the >>> Dell-provided web interface as opposed to mtx, so I don't think it's a >>> hardware issue - at least not with the tape changer itself. >>> >>> Any other thoughts/ideas/leads?? >>> >>> Thanks in advance! >>> Alden >>> >> >> -- >> +------------------------------------------------------------------+ >> | James W. Laferriere | System Techniques | Give me VMS | >> | Network&System Engineer | 3237 Holden Road | Give me Linux | >> | ba...@ba... | Fairbanks, AK. 99709 | only on AXP | >> +------------------------------------------------------------------+ >> >> >> ------------------------------------------------------------------------------ >> Storage Efficiency Calculator >> This modeling tool is based on patent-pending intellectual property that >> has been used successfully in hundreds of IBM storage optimization engage- >> ments, worldwide. Store less, Store more with what you own, Move data to >> the right place. Try It Now! >> http://www.accelacomm.com/jaw/sfnl/114/51427378/ >> _______________________________________________ >> Mtx-general mailing list >> Mtx...@li... >> https://lists.sourceforge.net/lists/listinfo/mtx-general >> > -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | ba...@ba... | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+ |
|
From: Alden T. <ald...@gm...> - 2011-08-05 17:53:08
|
Hi again, Thank you for the help. Sorry for the delay - we tried a new controller (Adaptec 2260300-R 2045 RAID), but unfortunately now the controller only sees our tape library as a tape drive, but not a changer: $ lsscsi -g [0:0:0:0] cd/dvd HL-DT-ST CDRW/DVD GCC4244 B101 /dev/sr0 /dev/sg0 [2:0:32:0] enclosu DP BACKPLANE 1.05 - /dev/sg1 [2:2:0:0] disk DELL PERC 6/i 1.22 /dev/sda /dev/sg2[3:3:0:0] tape IBM ULT3580-HH4 97F1 /dev/st0 /dev/sg3 $ cat /proc/scsi/scsi Attached devices: Host: scsi0 Channel: 00 Id: 00 Lun: 00 Vendor: HL-DT-ST Model: CDRW/DVD GCC4244 Rev: B101 Type: CD-ROM ANSI SCSI revision: 05 Host: scsi2 Channel: 00 Id: 32 Lun: 00 Vendor: DP Model: BACKPLANE Rev: 1.05 Type: Enclosure ANSI SCSI revision: 05 Host: scsi2 Channel: 02 Id: 00 Lun: 00 Vendor: DELL Model: PERC 6/i Rev: 1.22 Type: Direct-Access ANSI SCSI revision: 05 Host: scsi3 Channel: 03 Id: 00 Lun: 00 Vendor: IBM Model: ULT3580-HH4 Rev: 97F1 Type: Sequential-Access ANSI SCSI revision: 03 although now mt -f /dev/nst0 eject works, without the Input/Output error from before (after I've loaded a tape from the Dell web interface): $ mt -f /dev/nst0 status SCSI 2 tape drive: File number=0, block number=0, partition=0. Tape block size 0 bytes. Density code 0x46 (LTO-4). Soft error count since last status=0 General status bits on (41010000): BOT ONLINE IM_REP_EN $ mt -f /dev/nst0 eject $ echo $? 0 Is this just an incompatible raid controller? If so, then maybe to take a step back, has anyone found a good raid controller that will work with mtx for a Dell PowerEdge 2950 and a Dell TL 4000? This must be a fairly common combination... Thanks in advance! Alden On Mon, Jul 25, 2011 at 11:11 AM, Mr. James W. Laferriere < ba...@ba...> wrote: > Hello Alden , > > On Mon, 25 Jul 2011, Alden Timme wrote: > > Thanks for the continued help! Unfortunately, I still can't get it to > > work... > > > > I looked through the MTX FAQ (also here: > http://mtx.sourceforge.net/faq.html), > > and went through some of their suggestions for problems that looked > similar > > to mine (in III. Operational issues): > > - my mtx is not busted (this was happening on the Ubuntu native package > > version 1.3.12 and still on version 2.0.0 from svn) > > - my loader is in Random mode. I even switched it to Sequential to try it > > out and then back - no luck. I can't even get mtx status to work when in > > sequential mode, although I don't know if that is expected. > > - I tried each of mt {offline | rewoffl | eject}, and each time got the > > following error: > > > > $ mt -f /dev/nst0 eject > > /dev/nst0: Input/output error > > > > even though that is the path to the tape device: > > > > $ lsscsi -g > > [0:0:0:0] cd/dvd HL-DT-ST CDRW/DVD GCC4244 B101 /dev/sr0 /dev/sg0 > > [2:0:32:0] enclosu DP BACKPLANE 1.05 - /dev/sg1 > > [2:2:0:0] disk DELL PERC 6/i 1.22 /dev/sda /dev/sg2 > > [3:0:48:0] tape IBM ULT3580-HH4 97F1 /dev/st0 /dev/sg3 > > [3:0:48:1] mediumx IBM 3573-TL 8.40 /dev/sch0 /dev/sg4 > > I hope that (at worst) the Perc6/i is in 'Just a bunch of disks' > mode . > Even a that most 'Raid capable' controllers have fits when attaching > tape drives to them . > Try finding a plain scsi controller to attach the tape robot to & > use > that . Much less difficulties when going that route . > The clincher is that 'mt' doesn't seem to find the tape drive either > . > > Hth , JimL > > > One (perhaps) interesting thing is that mt -f /dev/nst0 {offline | > rewoffle > > | eject} takes a little while to show the error, and while I am waiting > for > > the mt command, I can see the drive status move from "Closed" to > "Unloading" > > and then back to "Closed" (without actually unloading). > > N.B. This is from the web/gui interface for the changer, which comes with > it > > as a Dell product. > > Also note that I was wrong (from my first post) about mt -f /dev/nst0 > > actually unloading the tape... > > > > Also, FYI I don't ever see any errors when loading/unloading using the > > Dell-provided web interface as opposed to mtx, so I don't think it's a > > hardware issue - at least not with the tape changer itself. > > > > Any other thoughts/ideas/leads?? > > > > Thanks in advance! > > Alden > > > > -- > +------------------------------------------------------------------+ > | James W. Laferriere | System Techniques | Give me VMS | > | Network&System Engineer | 3237 Holden Road | Give me Linux | > | ba...@ba... | Fairbanks, AK. 99709 | only on AXP | > +------------------------------------------------------------------+ > > > ------------------------------------------------------------------------------ > Storage Efficiency Calculator > This modeling tool is based on patent-pending intellectual property that > has been used successfully in hundreds of IBM storage optimization engage- > ments, worldwide. Store less, Store more with what you own, Move data to > the right place. Try It Now! > http://www.accelacomm.com/jaw/sfnl/114/51427378/ > _______________________________________________ > Mtx-general mailing list > Mtx...@li... > https://lists.sourceforge.net/lists/listinfo/mtx-general > |
|
From: Mr. J. W. L. <ba...@ba...> - 2011-07-25 18:11:30
|
Hello Alden , On Mon, 25 Jul 2011, Alden Timme wrote: > Thanks for the continued help! Unfortunately, I still can't get it to > work... > > I looked through the MTX FAQ (also here: http://mtx.sourceforge.net/faq.html), > and went through some of their suggestions for problems that looked similar > to mine (in III. Operational issues): > - my mtx is not busted (this was happening on the Ubuntu native package > version 1.3.12 and still on version 2.0.0 from svn) > - my loader is in Random mode. I even switched it to Sequential to try it > out and then back - no luck. I can't even get mtx status to work when in > sequential mode, although I don't know if that is expected. > - I tried each of mt {offline | rewoffl | eject}, and each time got the > following error: > > $ mt -f /dev/nst0 eject > /dev/nst0: Input/output error > > even though that is the path to the tape device: > > $ lsscsi -g > [0:0:0:0] cd/dvd HL-DT-ST CDRW/DVD GCC4244 B101 /dev/sr0 /dev/sg0 > [2:0:32:0] enclosu DP BACKPLANE 1.05 - /dev/sg1 > [2:2:0:0] disk DELL PERC 6/i 1.22 /dev/sda /dev/sg2 > [3:0:48:0] tape IBM ULT3580-HH4 97F1 /dev/st0 /dev/sg3 > [3:0:48:1] mediumx IBM 3573-TL 8.40 /dev/sch0 /dev/sg4 I hope that (at worst) the Perc6/i is in 'Just a bunch of disks' mode . Even a that most 'Raid capable' controllers have fits when attaching tape drives to them . Try finding a plain scsi controller to attach the tape robot to & use that . Much less difficulties when going that route . The clincher is that 'mt' doesn't seem to find the tape drive either . Hth , JimL > One (perhaps) interesting thing is that mt -f /dev/nst0 {offline | rewoffle > | eject} takes a little while to show the error, and while I am waiting for > the mt command, I can see the drive status move from "Closed" to "Unloading" > and then back to "Closed" (without actually unloading). > N.B. This is from the web/gui interface for the changer, which comes with it > as a Dell product. > Also note that I was wrong (from my first post) about mt -f /dev/nst0 > actually unloading the tape... > > Also, FYI I don't ever see any errors when loading/unloading using the > Dell-provided web interface as opposed to mtx, so I don't think it's a > hardware issue - at least not with the tape changer itself. > > Any other thoughts/ideas/leads?? > > Thanks in advance! > Alden > -- +------------------------------------------------------------------+ | James W. Laferriere | System Techniques | Give me VMS | | Network&System Engineer | 3237 Holden Road | Give me Linux | | ba...@ba... | Fairbanks, AK. 99709 | only on AXP | +------------------------------------------------------------------+ |
|
From: Alden T. <ald...@gm...> - 2011-07-25 18:00:36
|
Thanks for the continued help! Unfortunately, I still can't get it to work... I looked through the MTX FAQ (also here: http://mtx.sourceforge.net/faq.html), and went through some of their suggestions for problems that looked similar to mine (in III. Operational issues): - my mtx is not busted (this was happening on the Ubuntu native package version 1.3.12 and still on version 2.0.0 from svn) - my loader is in Random mode. I even switched it to Sequential to try it out and then back - no luck. I can't even get mtx status to work when in sequential mode, although I don't know if that is expected. - I tried each of mt {offline | rewoffl | eject}, and each time got the following error: $ mt -f /dev/nst0 eject /dev/nst0: Input/output error even though that is the path to the tape device: $ lsscsi -g [0:0:0:0] cd/dvd HL-DT-ST CDRW/DVD GCC4244 B101 /dev/sr0 /dev/sg0 [2:0:32:0] enclosu DP BACKPLANE 1.05 - /dev/sg1 [2:2:0:0] disk DELL PERC 6/i 1.22 /dev/sda /dev/sg2 [3:0:48:0] tape IBM ULT3580-HH4 97F1 /dev/st0 /dev/sg3 [3:0:48:1] mediumx IBM 3573-TL 8.40 /dev/sch0 /dev/sg4 One (perhaps) interesting thing is that mt -f /dev/nst0 {offline | rewoffle | eject} takes a little while to show the error, and while I am waiting for the mt command, I can see the drive status move from "Closed" to "Unloading" and then back to "Closed" (without actually unloading). N.B. This is from the web/gui interface for the changer, which comes with it as a Dell product. Also note that I was wrong (from my first post) about mt -f /dev/nst0 actually unloading the tape... Also, FYI I don't ever see any errors when loading/unloading using the Dell-provided web interface as opposed to mtx, so I don't think it's a hardware issue - at least not with the tape changer itself. Any other thoughts/ideas/leads?? Thanks in advance! Alden |
|
From: Kevin W. <kj...@po...> - 2011-07-23 00:58:21
|
From Alden Timme > I'm having an issue with errors from mtx when changing tapes (loading/ > unloading). > My guess is this is because it is still in the process of loading/unloading a > tape. that's my guess too it's hard to tell, but usually you rewind the tape and eject it before calling mtx to move the tape around. you should use mt to do tape drive operations, then follow up with mtx to perform tape robot arm operations. - Kevin |
11 messages has been excluded from this view by a project administrator.
