- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- No vfs nlock_record kernel parameter on Tru64 V4?
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
тАО02-22-2009 02:19 PM
тАО02-22-2009 02:19 PM
Operational: flckinfo.recmax ( 10000 ) is above 90% of nlock_record ( 10000 )
I try to perform the following kernel tuning:
/sbin/sysconfig -r vfs nlock_record=20000
nlock_record: unknown attribute
This parameter seems only to exist on Tru64 V5?
Questions:
* Why does sys_check on V4 warns me that this (non existing?) process parameter might be too low?
* How would I otherwise increase this parameter on a Tru64 V4 system?
I cannot upgrade to V5 because I run on an AlphaStation 500 ...
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2009 04:15 AM
тАО02-23-2009 04:15 AM
Re: No vfs nlock_record kernel parameter on Tru64 V4?
it states :
Some attributes in the following list have corresponding parameters in the system configuration file. If so, the corresponding parameter name in the system configuration file is specified in parentheses following the attribute name.
scrolling down to :
* nlock_record
Maximum number of record locks that may be held by a process. This limit prevents lock structures for any one process from consuming too much kernel memory.
=> no name in parentheses !
==> probably not configurable in sysconfigtab.
it's not clear to me yet what command can set this parameter.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2009 04:35 AM
тАО02-23-2009 04:35 AM
Re: No vfs nlock_record kernel parameter on Tru64 V4?
to see if the OS knows the variable at all
output from V5.1b system:
root@eagle # sysconfig -Q vfs nlock_record
vfs:
nlock_record - type=LONG op=CRQ min_val=1000 max_val=100000
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-23-2009 05:59 AM
тАО02-23-2009 05:59 AM
SolutionHOSTNAME represents the simple hostname in all uppercase characters.
1. Edit kernel configuration file:
# cd /sys/conf
# cp HOSTNAME HOSTNAME.backup
# vi HOSTNAME
...find options section and add this line:
options nlock_record = 20000
...exit vi
2. Rebuild the kernel:
# doconfig -c HOSTNAME
3. Copy the new kernel to root and reboot:
# cp /vmunix /vmunix.backup
# cp /sys/HOSTNAME/vmunix /vmunix
# shutdown -r now
4. If you want to verify that the change worked, do this after rebooting:
# dbx -k /vmunix
...unimportant warning messages appear...
(dbx) pd nlock_record
...should return "20000"
(dbx) quit
Hope this helps,
Martin
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2009 10:57 AM
тАО02-24-2009 10:57 AM
Re: No vfs nlock_record kernel parameter on Tru64 V4?
Apparently it is possible to change this parameter interactively, even on Tru64 V4, with the dbx command.
You can use "assign" - the system keeps the value until the next reboot:
dbx -k /vmunix
(dbx) p nlock_record
10000
(dbx) assign nlock_record=20000
20000
(dbx) p nlock_record
20000
(dbx) quit
The "patch" command allows you to change the kernel parameter in the /vmunix file (it will keep its value until the next kernel build).
Make a copy of the current kernel:
cp /vmunix /vmunix-20090224
dbx -k /vmunix
(dbx) patch nlock_record=20000
20000
(dbx) quit
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО02-24-2009 11:20 AM
тАО02-24-2009 11:20 AM
Re: No vfs nlock_record kernel parameter on Tru64 V4?
Martin
A quick resolution to technical issues for your HPE products is just a click away HPE Support Center
See Self Help Post for more details