Mounting LSM volumes after 5.1a install, from 4.0f

From: McCracken, Denise (Denise.McCracken@misyshealthcare.com)
Date: Thu Dec 19 2002 - 18:03:16 EST


        I've received a few suggestions on this that were helpful, but I'm
having one problem that is holding me up. When I try to mount my LSM
volumes, I get this message:

# mount /dev/vol/sqdg/sqtstvol /mnt
Error: partition /dev/vol/sqdg/sqtstvol is marked 'unused'.

        If I do a volprint, I get:

# volprint -g sqdg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0
PUTIL0
dg sqdg sqdg - - - - - -
 
dm sqdg01 dsk3 - 4109440 - - - -
 
v sqtstvol fsgen ENABLED 4109440 - ACTIVE - -
pl sqtstvol-01 sqtstvol ENABLED 4109440 - ACTIVE - -
sd sqdg01-01 sqtstvol-01 ENABLED 4109440 0 - - -

        This certainly looks like it would mount up. Where is it marked
"unused"?

thanks

-D

Denise McCracken
MiSys Healthcare Systems
Denise.McCracken@misyshealthcare.com
(520) 570-2521

-----Original Message-----
From: Jay R. Wren [mailto:jrwren@oakland.edu]
Sent: Tuesday, December 17, 2002 2:31 PM
To: tru64-unix-managers@ornl.gov
Subject: HSZ50 and Tru64 5.1A hwmgr

Hello Managers,

   I'm having a little problem with Tru64 and behavior with an HSZ50
(firmware 5.7). The server is an Alpha Server 4100 running Tru64 5.1A
PK3. hwmgr doesn't seem to like it when the HSZ50 has units on a given
scsi id on different LUNs. When I say "doesn't like it" I mean a scan
scsi doesn't seem to detect the device. The HSZ50 claims to support
units of 200-207, 300-307, 400-407, 500-507. This is 28 units, 7 luns
over 4 target id's. If I am limited to not using the LUNs that drops
me to only 4 units which is close to useless.

Am I misunderstanding how the HSZ50 interfaces with Tru64? Is there
something I must to do tell hwmgr that there may be disks on a
different lun on that bus?

--
Jay


This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:02 EDT