helgeson Absent Member.
Absent Member.
1557 views

OES2 SP2 NCP/Samba issue

I just upgraded to OES2 SP2 SLES 10.3 this past weekend. I'm seeing a very strange problem when I run smbstatus on my server to check samba services. i am seeing hundreds of open files but none of the users are using Samba. They login via Novell Client. Also, the files stay opened on samba, but closed on ncp when the user logs out. Does anyone has any ideas? We also have Shadow volumes implemented on this server, which also seems to be a part of the problem, since the open files go to the shadowfs/VOLUME/file path specified in the smb.conf. My other OES2 server does not have this problem and is NOT using shadow volumes.

Thanks!
Labels (2)
0 Likes
1 Reply
W_Prindl Absent Member.
Absent Member.

Re: OES2 SP2 NCP/Samba issue

Do those files actually really exist?

I have this problem: Samba locks are created for files in use by via
NCP, which is correct. Sometimes (mostly if the NCP client does not
shut down cleanly), deleted files retain their SAMBA-lock, despite of
the fact, that these files do not exist any more. These locks are
piling up until a restart of SMB occurs. This is due to the fact, that
SAMBA-locks for NCP-connections are maintained, by one single process
of smbd as long as SAMBA is running, whereas Samba connection locks are
maintained by an extra process for each user, and the locks of each
user are cleared at least if the Samba connection is closed and the
corresponding process is ended.
--
W. Prindl


helgeson wrote:

>
>I just upgraded to OES2 SP2 SLES 10.3 this past weekend. I'm seeing a
>very strange problem when I run smbstatus on my server to check samba
>services. i am seeing hundreds of open files but none of the users
>are using Samba. They login via Novell Client. Also, the files stay
>opened on samba, but closed on ncp when the user logs out. Does
>anyone has any ideas? We also have Shadow volumes implemented on
>this server, which also seems to be a part of the problem, since the
>open files go to the shadowfs/VOLUME/file path specified in the
>smb.conf. My other OES2 server does not have this problem and is NOT
>using shadow volumes.
>
>Thanks!


W. Prindl
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.