- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Hpux error 32 - filesys overflow
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
тАО11-26-2002 03:14 AM
тАО11-26-2002 03:14 AM
Hpux error 32 - filesys overflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 03:23 AM
тАО11-26-2002 03:23 AM
Re: Hpux error 32 - filesys overflow
Possibly, but more information is required.
From /usr/include/sys/errno.h, error 32 simply means 'Broken Pipe'.
What sort of database?
Are there any other meaningful error messages?
Was anything unusual happening?
Can you reproduce the problem?
Regards,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 03:24 AM
тАО11-26-2002 03:24 AM
Re: Hpux error 32 - filesys overflow
if you are speeking about a "filesystem overflow" then you can tune up the kernel parameter NFILE, but you should not tune this parameter directly, a better way is to increase MAXUSER.
Regards,
Armin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 03:28 AM
тАО11-26-2002 03:28 AM
Re: Hpux error 32 - filesys overflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 03:33 AM
тАО11-26-2002 03:33 AM
Re: Hpux error 32 - filesys overflow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 03:38 AM
тАО11-26-2002 03:38 AM
Re: Hpux error 32 - filesys overflow
You need to increase the kernel parameter 'nfile' and reboot.
You can check the status of the file table with 'sar -v 1'. The value in the column labelled file-sz is
Regards,
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-26-2002 03:45 AM
тАО11-26-2002 03:45 AM
Re: Hpux error 32 - filesys overflow
In general it's recommended not to modify kernel parameters directly but rather use indirect modifiers like MAXUSERS. In this case NFILE is a very cheap parameter which can really be put to a very big value (> 50000)without any impact on your system while other indirect modifiers would also increase NINODE for example (inode CACHE not a table size, not used by VxFs, very expensive in size and time and notoriously always too high). I talk about this one because 'sar -v' will probably tell you that it's almost full, although it's normal since it's a cache. The only parameter that you could relate to NFILE could be NFLOCKS which 'should' be around 10% of NFILE.
Regards.