Unjamming disks in limbo
- From: JF Mezei <jfmezei.spamnot@xxxxxxxxxxxx>
- Date: Fri, 30 Dec 2005 13:59:30 -0500
I have a bound volume set of DSSI disks on node VELO which is a 4000-600
and wheel, a 4000-200.
BIKE is a 3100 connected to the others ia ethernet.
I had a mishap where bike lost access to the drives long enough to lapse
mount verification (I was asleep).
One disk is a bound volume set.
$MOUNT/SYSTEM/CLU/BIND=CAMPY $4$dia1,$4$dia2,$4$dia3,$4$dia4,
CAMPAGNOLO,DISK42,DISK43,DISK44 $DISK2
Its current status is:
$4$DIA1: (VELO) MntVerifyTimeout 0 CAMPAGNOLO 2686734
2 2
dismount
$4$DIA2: (VELO) Mounted 0 (remote mount)
2
$4$DIA3: (VELO) Mounted 0 (remote mount)
2
$4$DIA4: (VELO) Mounted 0 (remote mount)
2
$ dismount $4$dia1
%SYSTEM-F-DEVNOTMOUNT, device is not mounted
>$MOUNT/SYSTEM/CLU/BIND=CAMPY $4$dia1,$4$dia2,$4$dia3,$4$dia4,
CAMPAGNOLO,DISK42,DISK43,DISK44 $DISK2
>%MOUNT-I-OPRQST, device is already mounted
>%MOUNT-I-OPRQST, device _$4$DIA1: (VELO) is not available for mounting.
<ctrl-Y>
*INTERRUPT*
$ exit
%MOUNT-I-OPRQSTCAN, operator request canceled
This hangs, with an operator request going to the OPA0:, but it isn't
obvious what the operator is supposed to do.
Disk $4$DIA1: (VELO), device type RF73, is online, mounted, mount verification
timed out, volume is marked for dismount, file-oriented device, shareable,
available to cluster, error logging is enabled.
Error count 0 Operations completed
24165
Owner process "" Owner UIC [SYSTEM]
Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W
Reference count 1 Default buffer size
512
Total blocks 3906420 Sectors per track
71
Total cylinders 2620 Tracks per cylinder
21
Host name "VELO" Host type, avail VAX
4000-600A, yes
Alternate host name "WHEEL" Alt. type, avail VAX
4000-200, no
Allocation class 4
Volume label "CAMPAGNOLO" Relative volume number
1
Cluster size 6 Transaction count
2
Free blocks 2686734 Maximum files allowed 490000
Extend quantity 24 Mount count
2
Mount status Process Cache name "_$2$DKA200:XQPCACHE"
Extent cache size 64 Maximum blocks in extent cache 268673
File ID cache size 64 Blocks currently in extent cache
0
Quota cache size 0 Maximum buffers in FCP cache
257
Volume owner UIC [SYSTEM] Vol Prot S:RWCD,O:RWCD,G:RWCD,W:RWCD
Volume Status: ODS-2, file high-water marking, write-back caching enabled.
Volume is also mounted on VELO1, VELO.
Members of this volume set are $4$DIA1: (rvn 1).
NOTE that it has lost the information about the volume set having 3
other drives.
The drives are in perfect working condition from the point of view of
VELO, and if I boot WHEEL, it doesn't have problems with them.
$4$dia5, a single drive seemed to fare much better and I was able to
dismount it and remount it on BIKE and is now working fine.
I tried DISMOUNT/ABORT/OVERRIDE=CHECKS and this is what got me into that
state of limbo.
Is there a way to force this set of devices to be reset on BIKE so that
BIKE could then start from scratch and mount them ? Or is a reboot of
BIKE truly the only way to fix this ?
What actually happens in a mount verification timeout ? I can understand
that during mount verification, VMS will delay completion of any io to
that device, so any app trying to access that drive just hangs. But once
it times out, shouldn't VMS automatically dismount the thing and returns
error messages for any IO done ?
.
- Prev by Date: Re: HP : Massive strike and protest march today
- Next by Date: Re: TLZ07/TLZ09 compatability
- Previous by thread: Replacing null characters with blanks in a text file
- Next by thread: OT: Intel logo and branding changes
- Index(es):
Relevant Pages
|
