- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: Mount-f-noslot when mounting new shadowset
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 12:02 PM
тАО03-02-2007 12:02 PM
Re: Mount-f-noslot when mounting new shadowset
--
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)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2007 12:43 AM
тАО03-03-2007 12:43 AM
Re: Mount-f-noslot when mounting new shadowset
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2007 02:36 AM
тАО03-03-2007 02:36 AM
Re: Mount-f-noslot when mounting new shadowset
>>>
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-03-2007 02:56 AM
тАО03-03-2007 02:56 AM
Re: Mount-f-noslot when mounting new shadowset
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2007 11:25 PM
тАО03-04-2007 11:25 PM
Re: Mount-f-noslot when mounting new shadowset
$ DIR/DAT OPC$LOGFILE_NAME
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2007 11:39 PM
тАО03-04-2007 11:39 PM
Re: Mount-f-noslot when mounting new shadowset
try searching for 'WBM'
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-04-2007 11:46 PM
тАО03-04-2007 11:46 PM
Re: Mount-f-noslot when mounting new shadowset
$ search
SEARCH-I-NOMATCHES
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2007 12:05 AM
тАО03-05-2007 12:05 AM
Re: Mount-f-noslot when mounting new shadowset
last reply should of course have been
$ search
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2007 01:15 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-05-2007 02:32 AM
тАО03-05-2007 02:32 AM
Re: Mount-f-noslot when mounting new shadowset
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