Re: %MOUNT-W-INCONSIZE

From: H Vlems (hvlems.nieuw_at_zonnet.nl)
Date: 10/05/03


Date: Sun, 5 Oct 2003 15:07:15 +0200


"Phillip Helbig---remove CLOTHES to reply" <helbig@astro.multiCLOTHESvax.de>
schreef in bericht news:blov67$2qu$1@online.de...
> Further adventures of a hobbyist cluster, continued.
>
> Experimenting with a VAX 4000 100A, I have a BA350 hooked up. It
> appears to have some sort of DSSI-to-SCSI adapter attached, and is
> attached to the big multi-function connector on the back of the machine.

Is it a DWZZA-nn perhaps?
>
> The system disk on this machine is a DSSI disk.
>
> I stuck in a couple of RZ28-VA disks, powered up the BA350, and did a
> SYSGEN AUTOCONFIGURE ALL.
>
> SHOW DEVICE now reports a different controller name than for the system
> disk (i.e. the "node name" in parentheses after the device name). It
> also has an allocation class which is the same as another node in the
> cluster.
The DSSI/SCSI bus converter behaves similar to an HSC50 in a CI cluster.
Where a DSSI disk has its own built-in controller that lets you set ALLCLASS
etc., SCSI disks do not have that feature of course. The DWZZA does that.
IIRC it also allows you to assign device names to the disks, so if you
prefer DUA names instead of DIA then the DWZZA will do that as well.
>
> I still have archived somewhere the information on how to change the
> allocation class and name of the DSSI controller.
>
$ help set host /dup

> At the moment, the DSSI controller with the system disk on it has the
> same allocation class as the VAX itself (i.e. for those disks which show
> up on the SCSI controller on the VAX, such as the CD-ROM drive).
>
> Would it make sense to give this new DSSI controller (I assume there are
> two separate controllers, rather than the connector on the back being an
> extension of the internal DSSI bus---otherwise the node names would be
> different, right?) the same allocation class which is in use on the rest
> of the machine (for the machine itself and for the other DSSI
> controller)?
>

As long as you do not add another DSSI VAX on that bus you can use the same
ALLOCLASS.

> The disks show up as $1$DIA10: etc in the BA350, so there would be no
> naming conflict with the internal disk ($5$DIA3:---of course the
> allocation classes would be the same if I change the 1 to 5 on the new
> controller connected to the BA 350).
>

It is one reason why you'd want a different ALLOCLASS value for the disks in
the BA35x cabinet. As long as the device names are not identical to already
present disks there's no problem.

> The two SCSI disks seem to be OK otherwise (i.e. when connected directly
> to a SCSI controller, they appear to work). MOUNT on the VAX now gives:
>
> %MOUNT-W-INCONSIZE, inconsistent number of blocks reported, some data
> may not be accessible
>
> What causes this message? Should I worry about it? What can I do to
> prevent it?
>
Perhaps the size? I can no longer remember the size of the largest RF disk,
was it 2 GB? So if you put in a 4 GB RZ29 then the DIdriver probably got
somewhat suprised. If you do have a DWZZA then you might work around that
problem by telling it to use DU device names.

Hans



Relevant Pages

  • Re: %MOUNT-W-INCONSIZE
    ... >>internal drives would probably then be SCSI instead of DSSI. ... > disks in the BA350 via DSSI and a further set of disks on the SCSI bus. ... So you have SCSI disks directly attached to the DSSI connector on ...
    (comp.os.vms)
  • Re: 4.3 BSD on a uVAX (KA630) ?
    ... Which release supports MSCP Disks and TMSCP boot? ... This is a problem only if you use DSSI ... The Emulex is sitting on the B-Bus and one of them emulates an TMSCP Controller and the other half an MSCP Controller. ...
    (comp.sys.dec)
  • Re: DSSI to BA23 question
    ... I'm wishing to learn about DSSI using the KFQSA ... The controller is the only DSSI component that ... My suggestion is to find a StorageWorks BA350 box and a HSD05 or HSD10 DSSI controller and some RZ*-VA disks and of course a cable from the rear panel to the HSD05/10. ...
    (comp.sys.dec)
  • Re: 6.2 not compatible with new sata drives ?!
    ... Some combinations of controller and drive do not play well ... I assume that the new failing disks are ... If your controller works well with your Samsung drives, ... Decided to try my origonal 6.2amd64 iso again, ...
    (freebsd-questions)
  • Re: Anyone seen this before?
    ... with an Adaptec 2110S RAID controller and a pair of disks. ... drive and home brewed cpio backup with a DVD writer and Microlite ... When testing the RE2 disaster recovery CD boot ...
    (comp.unix.sco.misc)