| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 319.1 | | COOKIE::FROEHLIN | Let's RAID the Internet! | Mon Feb 24 1997 11:18 | 13 |
| All member devices (incl. DSAnnn) are mounted /SYSTEM on all nodes
having the RAID Software running.
Could you explain a bit more on this:
> ... The problem comes later when something goes wrong and they want
>to dismount the devices -- it is inconvienent/unexpected/undesireable to have to
They don't have to do a DISMOUNT/CLUSTER per se. RAID Software does ALL
the mounting/dismounting.
Guenther
|
| 319.2 | | AMCFAC::RABAHY | dtn 471-5160, outside 1-810-347-5160 | Mon Feb 24 1997 11:31 | 29 |
| Testing confirms cluster-wide mount.
$ RAID INITIALIZE /RAID_LEVEL = 0 TEST $2$DKB100:,$2$DKB600:
$ RAID BIND /SHADOW TEST $2$DKB100:,$2$DKB600: DPA137:
$ SHOW DEVICE DSA6000
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA6000: Mounted 0 TEST00000000 32 2 2
$2$DKB100: (AMCFAC) ShadowSetMember 0 (member of DSA6000:)
Note the Mnt Cnt is 2.
Attempts to dismount the device from the other node fail;
$ DISMOUNT DSA6000:
%DISM-W-CANNOTDMT, DSA6000: cannot be dismounted
%DISM-W-USERFILES, 1 user file open on volume
Yet SHOW DEVICE /FILES doesn't show any open user file. ANALYZE /SYSTEM SHOW
PROCESS /CHANNEL for the RAID$SERVER process does *NOT* show a channel assigned
-- perhaps the Trans Count is incremented elsewhere?
The RAID SHUTDOWN command does dismount the device and those nodes without the
RAID software install never mount the device either. And, true to the online
help, it can't be restarted short of a reboot.
I guess what's being asked for here is something like a RAID BIND /NOCLUSTER
command.
|
| 319.3 | eh? | ORAREP::LASTOVICA | Comparisons are as bad as cliches | Mon Feb 24 1997 11:51 | 4 |
| Well since the DPA device is using the DSA device, it seems pretty
reasonable to me that you can not dismount the DSA device out from
under the RAID software. What about RAID UNBIND to dismount the
device? Does that do what you want?
|
| 319.4 | | COOKIE::FROEHLIN | Let's RAID the Internet! | Mon Feb 24 1997 15:51 | 14 |
| Quite right Norm! RAID$DPDRIVER increments the volumes's transaction
could faking an open file. Just to make sure that a volume is not
dismounted while RAID$DPDRIVER is firing low level I/Os to the device.
An UNBIND or SHUTDOWN decrements the transaction count.
RAID set member has gone into mount verify timeout an UNBIND does the
implicit DISMOUNT/ABORT per node but...if there are still DPA devices
mounted the UNBIND fails. The dismount of the DPA devices also fails
which in turn makes the UNBIND impossible which in turn does not clear
the mount verify timeout. Only a reboot clears it. Not good!
This issue is on the list of things-to-do for after V2.4.
Guenther
|