Hi Eric,
If I understand you correct.
You can define a drive and the path.
As soon you rename the drive the path is stop working?
And now you can't you update the path anymore or delete / define it again?
Have you compare the output from q drive f=d before and after rename?
Same thing with q path drive server srct=server f=d
Do also look on Devconf.out in your AIX filesystem. Maybe it tells you the
wrong path in their and have problem to update that file for you? (Security or
maybe something else)
Best Regards
Christian Svensson
Cell: +46-70-325 1577
E-mail: christian.svens...@cristie.se
Skype: cristie.christian.svensson
________________________________________
Från: ADSM: Dist Stor Manager [ads...@vm.marist.edu] för Loon, EJ van -
SPLXM [eric-van.l...@klm.com]
Skickat: den 1 juli 2009 22:47
Till: ADSM-L@VM.MARIST.EDU
Ämne: Re: Drive problem in AIX. I'm lost...
Hi Richard!
They are identical...
It must be a TSM issue then. I will try to create a path to the renamed drive
tomorrow (which will fail) and then try to create a path to the same drive on
the other TSM server on the same host. If that one does not fail, it must be
related to that specific TSM server instance (running the same TSM version) so
I will have to schedule a stop/start to see if that solves anything.
I'll keep you guys posted, thanks for now!
Kind regards,
Eric van Loon
________________________________
Van: ADSM: Dist Stor Manager namens Richard Rhodes
Verzonden: wo 7/1/2009 17:38
Aan: ADSM-L@VM.MARIST.EDU
Onderwerp: Re: Drive problem in AIX. I'm lost...
I don't have any real idea, but if it works as /dev/rmtX, and not after
renaming - I wonder if the binding is getting messed up on the rename.
Check the device attributes before the rename, and then after, and see if
the scsi_id, wwn, lun_id is the same.
lsattr -El rmt9
lsattr -El r123_4
"Loon, EJ van -
SPLXM"
<eric-van.l...@kl To
M.COM> ADSM-L@VM.MARIST.EDU
Sent by: "ADSM: cc
Dist Stor
Manager" Subject
<ads...@vm.marist Re: Drive problem in AIX. I'm
.EDU> lost...
07/01/2009 10:56
AM
Please respond to
"ADSM: Dist Stor
Manager"
<ads...@vm.marist
.EDU>
Hi Richard!
It's a virtual library from EMC in which I created two libraries, one
for the first TSM instance, the other one for the other instance. TSM1
uses the renamed devices (/dev/253 with drives /dev/253_0 to 29) and I
could create paths to the drives succesfully on that TSM instance. On
the other TSM instance, I can only use the devices as long as the name
starts with rmt. As soon as I rename them to 254_0 to 29 (our standard
naming convention) I receive an I/O error when I try to create the path.
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of
Richard Rhodes
Sent: woensdag 1 juli 2009 16:24
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Drive problem in AIX. I'm lost...
I'm a little confused on what you are trying to do. Is this one new lib
being shared between 2 instances via library sharing (one set of rmt/smc
devices), or, 2 new libs - one for each tsm instance (separate sets of
rmt/smc devices - one set to each tsm instance)?
Also, are you using Atape multi pathing?
"Loon, EJ van -
SPLXM"
<eric-van.l...@kl
To
M.COM> ADSM-L@VM.MARIST.EDU
Sent by: "ADSM:
cc
Dist Stor
Manager"
Subject
<ads...@vm.marist Drive problem in AIX. I'm lost...
.EDU>
07/01/2009 10:00
AM
Please respond to
"ADSM: Dist Stor
Manager"
<ads...@vm.marist
.EDU>
People, please help me, I'm lost...
We are running two TSM instances on one AIX host. I'm trying to create a
new library on both of them. The first one was no problem and everything
went as expected.
We have always used a script which renames the library an drives
detected by cfgmgr to math the SCSI id of the library. So if a smc0
(SCSI id 254) and a rmt0 is found, the script renames the library to
/dev/254 and the drive to /dev/254_0.
The script uses the command chdev -l <rmtdevice> -a
new_name=<scsid_drivenumber> to do this.
Now, on one of my servers, I cannot create a path to renamed drive! I
can create a path to /dev/rmt0, but as soon as I rename it to /dev/254_0
I get an I/O error when I try to create the path.
To make it even stranger: when I rename the drive to rmteric, I can
create a path successfully! But the name rmeric (so whithout the t)
results in the I/O error again.
I really cannot find the cause, especially since everything works as
expected on the other TSM instance on the same host!!!
Does anybody out there have any idea what could cause this strange
behavior???
Thank you VERY much in advance for any help!
Kind regards,
Eric van Loon
KLM Royal Dutch Airlines
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com <http://www.klm.com/> . This e-mail and any attachment may
contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**********************************************************************
-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If
the reader of this message is not the intended recipient or an
agent responsible for delivering it to the intended recipient, you
are hereby notified that you have received this document in error
and that any review, dissemination, distribution, or copying of
this message is strictly prohibited. If you have received this
communication in error, please notify us immediately, and delete
the original message.
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com <http://www.klm.com/> . This e-mail and any attachment may
contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**********************************************************************
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message.
Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286
**********************************************************************
