similar to: Could not delete share entry

On 2020-03-30 14:33, Rowland penny via samba wrote: > It might help if you don't crop lines like the above from your logs, out > of context they are meaningless. > > If you are going to post log fragments, post the entire log fragment and > a few lines above and below it. Sorry. Here a full excerpt: > [2020/03/30 14:56:31.559263, 0]

On 2020-03-31 11:38, Rowland penny via samba wrote: > I wouldn't worry about those, they are just warnings that something is > trying to delete something that it shouldn't or cannot. i.e something > that has already been deleted or it doesn't have the permission to delete. Well, I guess so :) Any hint on what that "something" is? What is a "share

On 2020-03-31 12:21, Rowland penny via samba wrote: > A 'share entry' is exactly that, a file or directory You mean, it's a client trying to delete a file/directory? From what I can see, crossing smbd's log and audit log, the message > [2020/03/30 15:23:16.754076, 0] ../../source3/smbd/close.c:1214(close_directory) > close_directory: Could not delete share entry

This with Samba 4.4.3 on Solaris 10. I have been looking at the logs and see messages such as: [2016/06/13 14:20:37.074011, 0] ../source3/smbd/oplock.c:242(remove_oplock) remove_oplock: failed to lock share entry for file packages/winnt/adv084/8.4.1/8.4.1.6.iso [2016/06/13 14:20:37.075061, 0] ../source3/smbd/close.c:266(close_remove_share_mode) close_remove_share_mode: Could not get share

Encountering a strange one... has been occuring since samba 4.15.x and continues to occur even in 4.17.5 and 4.18 Issue does not occur in earlier versions (4.13.x) and have switched back and forth between versions to confirm. Servers are winbind joined, PAM and krb5 auth, all seems to work fine (reading, writing, creating, moving) until trying to delete an empty folder on the share from Windows

Sorry for my previous email it was something wrong with my email client. Now is the corrected version: Hello, I have a problem with files locks on share. My server is running FreeBSD 10.2 (amd64) with ZFS pool (raidz) for windows share and samba 4.3.3 (ROLE_ACTIVE_DIRECTORY_DC). The server has approximately 100 users accounts and computers accounts. >From one windows workstation I open a

On Wed, Mar 15, 2023 at 04:53:16PM +0000, Rowland Penny via samba wrote: > > >On 15/03/2023 16:47, Jeremy Allison via samba wrote: >>On Wed, Mar 15, 2023 at 11:29:10AM -0400, CaptainTrips28 via samba wrote: >>>Encountering a strange one... has been occuring since samba 4.15.x and >>>continues to occur even in 4.17.5 and 4.18 >>> >>>Issue does not

> On Tue, Jun 28, 2016 at 11:59:32AM -0400, Thomas Schulz wrote: >> This with Samba 4.4.3 on Solaris 10. >> >> I have been looking at the logs and see messages such as: >> >> [2016/06/13 14:20:37.074011, 0] ../source3/smbd/oplock.c:242(remove_oplock) >> remove_oplock: failed to lock share entry for file packages/winnt/adv084/8.4.1/8.4.1.6.iso >>

Dear all, we updated to 4.12.10-10 using the sernet packages. After approx. 30 minutes I obtainted the following messages in syslog: root at ctdb-ho-2:~# journalctl -f -- Logs begin at Wed 2020-11-11 08:53:27 CET. -- Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: [2020/11/13 13:00:18.616823, 0] ../../source3/smbd/close.c:1150(close_directory) Nov 13 13:00:18 ctdb-ho-2 smbd[30956]: close_directory:

Hi, I'm hoping somebody can point me in the right direction. My samba version is samba-4.2.10-6.2.el7_2.x86_64. I have lots of daily core dumps (~20 on each machine daily) and I have no clear idea why. I'm including the stack trace below. It looks like the problem is related to "invalid lock_order". Any ideas? Thanks, Sergei #0 0x00007fc5a34945f7 in raise () from

Hello, I have a problem with files locks on share. My server is running FreeBSD 10.2 (amd64) with ZFS pool (raidz) for windows share and samba 4.3.3 (ROLE_ACTIVE_DIRECTORY_DC). The server has approximately 100 users accounts and computers accounts. >From one windows workstation I open a file e. g. text file (file.txt) the smbstatus shows DENY_WRITE and everything seems right. But when I open

Hi all Follow up to this post, as it didn't seem to go through the first time. We have a common problem occurring with our Samba setups. We run 3 (identical) processing environments that each contain a Samba host sharing approx .5TB of data to 6 Wintel machines. Normally these hosts operate fine, though we intermittently experience a Samba panic (intermittent = every 2-3 days) as per below.

Hey folks... I'm using the Redhat Samba package (samba-3.0.33-3.15.el5_4.1) and I'm having a problem with one specific user. When she opens a project for her program, there are several shape files which need to open. Unfortunately, performance is EXTREMELY slow for her; everyone else who accesses the project can open it up quickly and normally. A tail of /var/log/samba/<IP

Le 25/11/2019 ? 09:15, L.P.H. van Belle via samba a ?crit?: > I tested Friday also with a W7 pc. > Not working, im try to see what i can do today on this problem. > > Greetz, > > Louis Hi Louis, Thanks for your help. I'm still investigating on it, but sadly i cannot upgrade to 4.11 as those servers cannot reach external repositories for security reasons (those servers

Dear list, I have a question about the interaction between R code and Latex language trough the Sweave function in the package "utils". What I'm trying to do is to write a report. Contrary to the examples shown in the Sweave Manual in which table already constructed by R are "exported" on Latex files, what I would like to do is to build a table in which I combine text and

On Fri, 6 Jan 2017 22:28:11 -0600 Sergei Gerasenko via samba <samba at lists.samba.org> wrote: > Hi, > > I'm hoping somebody can point me in the right direction. My samba > version is samba-4.2.10-6.2.el7_2.x86_64. I have lots of daily core > dumps (~20 on each machine daily) and I have no clear idea why. I'm > including the stack trace below. It looks like the

Hi guys I have a problem with Samba 4.0 shares covered by scannedonly VFS. Example configuration of one of those shares: path = /foo/bar/baz read only = No browseable = No vfs objects = scannedonly scannedonly:domain_socket = True scannedonly:socketname = /var/lib/scannedonly/scan scannedonly:hide_nonscanned_files = True scannedonly:allow_nonscanned_files = False Whenever I

Release Announcements --------------------- This is the latest stable release of the Samba 4.15 release series. Changes since 4.15.3 -------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 14928: Duplicate SMB file_ids leading to Windows client cache ???? poisoning. ?? * BUG 14939: smbclient -L doesn't set "client max protocol" to NT1 before ???? calling the

Release Announcements --------------------- This is the latest stable release of the Samba 4.15 release series. Changes since 4.15.3 -------------------- o? Jeremy Allison <jra at samba.org> ?? * BUG 14928: Duplicate SMB file_ids leading to Windows client cache ???? poisoning. ?? * BUG 14939: smbclient -L doesn't set "client max protocol" to NT1 before ???? calling the

This is just a information in case somebody runs into the same issue: I was unable to upload drivers to a samba-server (3.0.28a and 3.0.29) via the windows add printer wizard. The driver files started uploading, then processing stopped saying the driver is not compatible to windows xp. In the logs the following message popped up. However some files could be copied: [2008/05/27 10:30:09, 0]