GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: CIFSCLIENT daemon coredump
Operating System - HP-UX
1849550
Members
6697
Online
104044
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
07-30-2003 04:42 AM
07-30-2003 04:42 AM
CIFSCLIENT daemon coredump
Hi,
I'm facing a serious problem with CIFSCLIENT.
A Win2K share (beh, really a high-availability share on a NAS Cluster...) is mounted by CIFSCLIENT on a HP-UX 11.00 machine.
Every long-running task on this filesystems aborts with a 'NFS/RPC timeout', leaving a stale mountpoint and a 'core' file in /var/opt/cifsclient/core directory.
I tried also with latest CifsClient version A.01.09.
Any idea?
I'm facing a serious problem with CIFSCLIENT.
A Win2K share (beh, really a high-availability share on a NAS Cluster...) is mounted by CIFSCLIENT on a HP-UX 11.00 machine.
Every long-running task on this filesystems aborts with a 'NFS/RPC timeout', leaving a stale mountpoint and a 'core' file in /var/opt/cifsclient/core directory.
I tried also with latest CifsClient version A.01.09.
Any idea?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2003 05:03 AM
07-30-2003 05:03 AM
Re: CIFSCLIENT daemon coredump
Hi,
Have you tried running a comparison on a Windows box? ie mapping the share and performing a similar task.
If the problem is only seen on CIFSclient, then I'd suggest you might need to tune some of the options. Full documentation for these is available under /opt/cifsclient/HP_Docs. The sections I'd concentrate on are: nfsTimeout and nfsRetransmit.
regards,
Darren.
Have you tried running a comparison on a Windows box? ie mapping the share and performing a similar task.
If the problem is only seen on CIFSclient, then I'd suggest you might need to tune some of the options. Full documentation for these is available under /opt/cifsclient/HP_Docs. The sections I'd concentrate on are: nfsTimeout and nfsRetransmit.
regards,
Darren.
Calm down. It's only ones and zeros...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2003 05:59 AM
07-30-2003 05:59 AM
Re: CIFSCLIENT daemon coredump
This might be a networking issue on the HP-UX box.
Please check out the following things.
lanadmin -x #
replace # with the 1 in lan1, whatever NIC is doing the connection.
If its not what you expect, it can cause the problem.
lanadmin -X 1 100FD
100 BaseT Full Duplex.
Check again.
If indeed these changes make the problem go away you can hard code your duplex settings in the file /etc/rc.config.d/hpbtlanconf
I am attaching an example file.
If you are going through a Cisco switch, have the HP-UX port setting set explicitly to 100 BaeT Full Duplex Manual if your NIC is not a 1000 BaseT NIC.
The above solution has solved CIFS/NFS and other networking issues for me in the past.
SEP
Please check out the following things.
lanadmin -x #
replace # with the 1 in lan1, whatever NIC is doing the connection.
If its not what you expect, it can cause the problem.
lanadmin -X 1 100FD
100 BaseT Full Duplex.
Check again.
If indeed these changes make the problem go away you can hard code your duplex settings in the file /etc/rc.config.d/hpbtlanconf
I am attaching an example file.
If you are going through a Cisco switch, have the HP-UX port setting set explicitly to 100 BaeT Full Duplex Manual if your NIC is not a 1000 BaseT NIC.
The above solution has solved CIFS/NFS and other networking issues for me in the past.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP