Mount-f-noslot when mounting new shadowset

[Robert Brooks_1]

You have more than 12 write bitmaps in the system, that's causing the ss$_noslot error.

--

There's a limit of 12 bitmaps per shadow set
(6 minicopy and 6 host-based minimerge),
but there is no limit systemwide (other than memory constraints).

I'll make sure the MOUNT maintainer hears about this one -- I'm curious to see who is actually returning NOSLOT.

-- Rob (ex-VMS Engineering, but still with HP)

[Volker Halle]

Louis,

did you check for existing device bitmaps on the shadowset(s) ?

$ SHOW DEV/BITMAP D

If there are old device bitmaps hanging around, you can delete them with $ DELETE/BITMAP xxx

The WBM facility (Write Bit Map) also reports errors into OPERATOR.LOG, did you check there ?

SS$_NOSLOT is being return with the WBM code (no more WBME entry slots available). This information should be added to the NOSLOT message help text.

Volker.

[Jan van den Ende]

Volker,

>>>
did you check for existing device bitmaps on the shadowset(s) ?
<<<

The drive was INITed just seconds before the first attempt to mount it, to create an entirely new, previously non-existing shadow set.

>>>
The WBM facility (Write Bit Map) also reports errors into OPERATOR.LOG, did you check there ?
<<<

We did not do that, Will do monday, and add that info.


>>>
SS$_NOSLOT is being return with the WBM code (no more WBME entry slots available). This information should be added to the NOSLOT message help text.
<<<

Not entirely clear what exactly you mean here (probably my lack of knowledge)
The reported error was MOUNT-F-NOSLOT. No secondairy message, nothing about WBM or WBME.

If Jur and Robert are indeed on the right track, then I agree, an addition to the HELP/MESSAGE text would be appropriate.

Proost.

Have one on me.

jpe

[Volker Halle]

Jan,

MOUNT itself does not return SS$_NOSLOT. The WBM (Write Bit Map) routines in the IO subsystem may return this error. The WBM-routines are called when mounting a shadowed disk. They also issue a message via OPCOM, as you will most probably find out on monday.

Volker.

[Jan van den Ende]

Okay, new (negative) results.

$ DIR/DAT OPC$LOGFILE_NAME
:OPERATOR.LOG 20-FEB-2007
Other node similar.
$ SEARCH those for DSA23 (intended shadowset) NOMATCHES
SEARCH for noslot -- no matches
search for mount-f- -- no matches

Any more ideas?

Proost.

Have one on me.

jpe

[Volker Halle]

Jan,

try searching for 'WBM'

Volker.

[Jan van den Ende]

Volker,

$ search
SEARCH-I-NOMATCHES

Proost.

Have one on me.

jpe

[Jan van den Ende]

Oops.

last reply should of course have been

$ search wbm

Proost.

Have one on me.

jpe

[Volker Halle · Accepted solution]

Jan,

I have seen WBM OPCOM messages like this:

Message from user WBM$SERVER
%WBM-I-WBMINFO No more bitmaps slots available

Does the problem still exist ? If so, try REPLY/ENABLE and repeat the failing mount command.

Volker.

[Jan van den Ende]

AIAIAIAIAIAI !

I _HOPE_ we have found the cause.

It seems that the system was configured by an overly "economic" person, who wanted to save a few KB of memory (on 4 GB systems!)

SYSGEN param SHADOW_MAX_UNIT is set as 20 !!!

It looks like a reboot cycle coming up.

As an aside:

I really would have appreciated if the error message had been more relevant, ie, more in line what we have come to expect from VMS!

After the reboots we will report the results.

Proost.

Have one on me.

jpe