Hi,
thanks to the following authoritative statement from the TruCluster product
manager Bob Grosso who states that mcutil can only be run on the machine
that is the current DRD server for the Media Changer ie probably the first
one booted, as empirically observed. The TruCluster team will address this
in a future release. I guess the solution is to relocate the device to the
desired machine using drdmgr. Detailed responses follow:
From: Bob Grosso [mailto:grosso_at_zk3.dec.com]
Sent: 15 August 2000 20:17
To: Luchini, Marco
Cc: Bob Grosso
Subject: Re: Media changers under TruCluster5.0A
Marco,
The TruCluster release notes state that you can only run mcutil on the
machine that is the current DRD server for the MC. [It is also likely
that the 1st machine booted would be the DRD server, hence your
observations.] We are trying to address this in a future release.
Bob Grosso
TruCluster Prd. Mgr.
-----Original Message-----
From: alan_at_nabeth.cxo.dec.com [mailto:alan_at_nabeth.cxo.dec.com]
Sent: None
To: Luchini, Marco
Subject: Re: Media changers under TruCluster5.0A
I suspect that the first node to touch the media changer
device does a Reserve to ensure it has exclusive access
to the device. mcutil and MRU work through a level of
the media changer driver that won't report low level
SCSI errors. However, if you use scu(8) to ship commands
to the device it may return more useful information.
I've heard of the symtom before, but I don't know the
details of what the problem is. My best educated guess
is that the device is reserved, which should be easy
enough to check.
-----Original Message-----
From: Viktor Holmberg [mailto:Viktor.Holmberg_at_tnsofres.com]
Sent: 15 August 2000 15:53
To: 'Luchini, Marco'
Subject: RE: Media changers under TruCluster5.0A
Marco,
There is a know problem with 5.0A where one node of a cluster can access the
disks/tapes and the other nodes can not. I had a similar problem with some
disks and the solution was patchkit-1 which was released 2 weeks ago. It
does take a bit of time to install.
Viktor
-----Original Message-----
From: Luchini, Marco [mailto:Marco.Luchini_at_acco-uk.co.uk]
Sent: 15 August 2000 15:47
To: tru64-unix-managers_at_ornl.gov
Subject: Media changers under TruCluster5.0A
Hi,
I'm unable to access the machines in question - telephone contact only - so
I'm not sure about the full details. So I'd like a sanity check about what
should and shouldn't work.
* TL891 on a shared bus in a 3 machine TruCluster 5.0A. mcutil on one node
works fine. /etc/mcicap is set up etc.
* problem is that the other nodes can't use mcutil. It returns "unknown
error". robot returns something along the lines of can't access the devices
but I don't have the details. The following:
hwmgr -scan scsi
drdmgr -a CHECK_PATH /dev/ntape/tape0
drdmgr -a CHECK_PATH /dev/changer/mc0
claimed that the path existed on the nodes that can't run mcutil.
* customer suspects that the only node that can run mcutil is the one that's
booted first.
a) is this supposed to work? I know that various utilities like dump etc
have not been adapted for cluster use in their response to bus resets but
there's no mention of mcutil. The release notes for 5.0A state that you can
share a media changer on the bus.
b) where else should I look?
Thanks
Marco
Marco Luchini
Unix support
Acco-Europe
**** DISCLAIMER ****
This e-mail and any attachments thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the recipient(s) named above. Any use of the information contained herein (including, but not limited to, total or partial reproduction, communication or distribution in any form) or the taking of any action in reliance on the contents, by persons other than the designated recipient(s) is strictly prohibited.
If you have received this e-mail in error, please notify the sender either by telephone or by e-mail and delete the material from any computer.
Thank you for your cooperation.
Received on Wed Aug 16 2000 - 13:14:32 NZST