Hi Bernaldo,
We also run TSM on HP-UX. I don't recall ever seeing that exact message,
but my guess is you either have a hardware problem with those two devices
(or something along the path to those devices... are they on the same FC
adapter or SCSI bus?),
-- OR --
HP-UX has renumbered the device files. I have had that happen, and I'm not
sure why... To be sure, you should do an 'ioscan -fnC tape' and compare it
to the files in /dev/rmt ('ls -l /dev/rmt'). If the devices have been
givien new instance numbers, I have found that the easiest, surest fix is
to delete the drives and paths from TSM and redefine them. You should also
remove any old unused special files from /dev/rmt by doing 'rmsf -a
/dev/rmt/23m' (for example). That command will remove the definition from
the kernel and all of the special files that were associated with that
device... 23m, 23mn, 23mb, 23mnb.
HTH
Regards,
Robin Sharpe
Berlex Labs
"Bernaldo de
Quiros, Iban 1"
<iban.bernaldodeq To
[EMAIL PROTECTED]> ADSM-L@VM.MARIST.EDU
Sent by: "ADSM: cc
Dist Stor
Manager" Subject
<[EMAIL PROTECTED] TSM Blocks Device Files in HP-UX
.EDU> after using it...
07/31/2006 05:27
AM
Please respond to
"ADSM: Dist Stor
Manager"
<[EMAIL PROTECTED]
.EDU>
Hi Everyone !!
Did anyone got this error on TSM ¿? any information or GOTCHA's ¿?
07/28/06 12:54:47 ANR9999D mmsext.c(1360): ThreadId<70> Unable to
obtain
model type for '/dev/rmt/25m', rc = 30 Callchain
follows:
0000000000d18e6f outDiagf+0x25f <-
0000000000e7005b
ExtMountVolume+0xe53 <- 000000000088fbff
MmsMountVolume+0x3ff <- 0000000000e0a0c7
PvrGtsOpen+0x9a7
<- 0000000000e5fa07 TapiOpen+0x247 <-
000000000083ce1f
AgentThread+0x7d7 <- 000000000012edb3
StartThread+0x17b
<- 000000000006b47b *UNKNOWN* <- (SESSION: 506)
07/28/06 15:58:00 ANR9999D mmsext.c(1360): ThreadId<60> Unable to
obtain
model type for '/dev/rmt/23m', rc = 30 Callchain
follows:
0000000000d18e6f outDiagf+0x25f <-
0000000000e7005b
ExtMountVolume+0xe53 <- 000000000088fbff
MmsMountVolume+0x3ff <- 0000000000e0a0c7
PvrGtsOpen+0x9a7
<- 0000000000e5fa07 TapiOpen+0x247 <-
000000000083ce1f
AgentThread+0x7d7 <- 000000000012edb3
StartThread+0x17b
<- 000000000006b47b *UNKNOWN* <- (SESSION: 31)
After appearing this issues on actlog, TSM do not release the device file,
so device file remains busy. The only solution that I find at the moment is
to halt the TSM server to release device files.
When I re-start the TSM it could access the device files normally until
this issue occurs another time...
OS VERSION HP-UX 11.00
TSM 5.2.6.3
Using HP-UX Generic Driver to access tapes (stape).
Working with GRESHAM EDT 7.4.0.5.
Any help will be appreciated.
Thanks in Advance,
Regards,
Ibán Bernaldo de Quirós Márquez
Technical Specialist
cell: + 34 659 01 91 12
Sun Microsystems Iberia
