- 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 03:10 AM
тАО03-02-2007 03:10 AM
I am new to this forum. I have the following problem:
When mounting a new shadowset on an Alpha ES45 using VMS V7.3-2 i get the error message:
%mount-f-noslot, no PCB available. Has anyone a suggestion as how to overcome this error? Any help will be appreciated.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 03:25 AM
тАО03-02-2007 03:25 AM
Re: Mount-f-noslot when mounting new shadowset
NOSLOT, no PCB available
Facility: SYSTEM, System Services
Explanation: The maximum number of processes that can be created at one
time has been exceeded.
User Action: Wait for another process to be deleted, or increase the
MAXPROCESSCNT system parameter.
How much don't you know about changing system
parameters like MAXPROCESSCNT?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 03:42 AM
тАО03-02-2007 03:42 AM
Re: Mount-f-noslot when mounting new shadowset
You've already been pointed to MAXPROCESSCNT, the other part of this is to look at what is present in the MODPARAMS.DAT file -- that's a common spot for tuning a system, and an equally common spot for mistuning a system -- and find out of it makes sense. I've seen all manner of parameter settings embedded there that are outdated (whether due to subsequent application or OpenVMS changes, or old information on system tuning), or should have been entered as MIN_, MAX_ or ADD_ parameter settings and that were erroneously inserted into MODPARAMS as absolute settings.
The contents of MODPARAMS can and do constrain what AUTOGEN can do to tune the settings, and what values it can establish.
In this case, I'd look at what's in MODPARAMS with a particular eye toward any process-level settings and any (absolute) setting of MAXPROCESSCNT, clean out any cruft, and where the values are still required I'd switch to MIN_, MAX_, or ADD_ where appropriate, and would AUTOGEN with FEEDBACK.
You can then begin an investigation of physical memory and process quotas. But the immediate NOSLOT limit can be lifted by using a MIN_MAXPROCESSCNT setting and an AUTOGEN (with FEEDBACK, and reboot) pass, or by reducing the numbers of currently active processes.
There is some risk to AUTOGEN, in that there are also folks that make system parameter settings changes directly, using SYSGEN or SYSMAN, and these changes can be lost over any subsequent AUTOGEN pass, and this AUTOGEN that can be required by a subsequent product installation, ECO, or OpenVMS upgrade. (Tweaking a parameter directly without also tweaking it in MODPARAMS is a common mistake. Most everybody makes it once.)
Ok, enough verbiage. Tweak MAXPROCESSCNT up via MODPARAMS and AUTOGEN FEEDBACK and reboot, or remove a few non-system, non-critical processes and continue running until you can schedule the tweak and the reboot.
Stephen Hoffman
www.HoffmanLabs.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 05:21 AM
тАО03-02-2007 05:21 AM
Re: Mount-f-noslot when mounting new shadowset
(now online) Louis: WELCOME to the VMS Forum.
Ok.
Background: I am a collegue of Louis, but because I will be incommunicado for nearly two weeks beginning next monday, we decided that it would be better to have someone else to deal with responses and further questions.
Now the problem.
- cluster environment, currently two nodes.
- current process counts just under & just over 1 K
- MAXPROCESSCOUNT both 3 K
- BALSETCOUNT both 2998
- 20 two-member shadow sets mounted clusterwide (20th set successfully mounted just minutes before)
- MOUNT
- MOUNT/SYSTEM
- MOUNT set /SHADOW=
The error is
%MOUNT-F-NOSLOT,
but HELP/MESS NOSLOT does _NOT_ mention MOUNT as a facility that should display the error.
Now, I at least was out of options.
Hope you can help.
Proost.
Have one on me.
jpe
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 06:17 AM
тАО03-02-2007 06:17 AM
Re: Mount-f-noslot when mounting new shadowset
Have you checked your shadowing license? Maybe you don't have the traditional unlimited license and have a restriction as to number of shadow disks?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 06:49 AM
тАО03-02-2007 06:49 AM
Re: Mount-f-noslot when mounting new shadowset
Gotta put that shadow server process somewhere.
Here's an old description of the overhead of shadowing...
http://h71000.www7.hp.com/wizard/wiz_4407.html
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 06:58 AM
тАО03-02-2007 06:58 AM
Re: Mount-f-noslot when mounting new shadowset
I really think it's a license problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 07:02 AM
тАО03-02-2007 07:02 AM
Re: Mount-f-noslot when mounting new shadowset
Jur.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 07:17 AM
тАО03-02-2007 07:17 AM
Re: Mount-f-noslot when mounting new shadowset
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-02-2007 07:26 AM
тАО03-02-2007 07:26 AM
Re: Mount-f-noslot when mounting new shadowset
do you mean that is a hard limit??
Sounds rather, or more than, extreme, seeing that write bitmaps are a rather recent devellopment, and the total of allowed shadowsets has for a very long time now been "limited" to 600 members, ie, 200 3-member sets or 300 2-member sets.
If the limit can be influenced, the gold medal question of course is:
The magic incantation, please, master?
But, at least it is the first explanation that is not at odds with the observations!
Proost.
Have one on me.
jpe