similar to: Error when removing kernel oplock

Hi All, Need your help/inputs on what could be the probable cause/how to debug this further. We are using samba-4.0.25 & expose a share that has oplocks enabled & no kernel-oplocks set. We constantly see these messages in samba logs [2015/06/25 03:05:30.593150, 0, pid=1581, class=locking] ../source3/smbd/oplock_linux.c:184(linux_release_kernel_oplock) linux_release_kernel_oplock:

I've been using Samba for a number of years and suddenly Samba started throwing oplock errors and I simply can't figure out why. I've not changed any config parameters in some time, but have updated my version of samba as new packages become available for my distro. I'm running Centos 5.9 and the following versions of samba from stock Centos: samba3x-common-3.6.6-0.129.el5

Hi Volker, Yes this problem happens when we have "kernel oplocks = no". This happened constantly in one of production systems & so we disabled level2-oplock /set kernel-oplocks=yes (to avoid this issue). So unfortunately don’t have an environment where it reproduces now & cannot capture strace. I modified smbtorture/smb2 to do a test exactly like the tcpdump trace, but the

On Thu, Jul 09, 2015 at 10:39:58AM +0530, Shyam Kaushik wrote: > Hi All, > > Need your help/inputs on what could be the probable cause/how to debug > this further. > > We are using samba-4.0.25 & expose a share that has oplocks enabled & no > kernel-oplocks set. We constantly see these messages in samba logs > > [2015/06/25 03:05:30.593150, 0, pid=1581,

Hi Volker, Thanks for your reply. When the problem was happening(before we turned off level2-oplocks), we had captured one run with smbd debug all:10 (unfortunately we didn’t setup for other modules like vfs etc). Can you please see if this below trace helps? Thanks. [2015/06/25 03:05:30.408432, 3, pid=1581, effective(2030299, 2000514), real(2030299, 0)]

https://bugzilla.mindrot.org/show_bug.cgi?id=3161 Bug ID: 3161 Summary: ssh -J <public IPv6> <LL IPv6%scopeID> doesn't work as expected Product: Portable OpenSSH Version: 8.2p1 Hardware: 68k OS: Mac OS X Status: NEW Severity: enhancement Priority: P5

https://bugzilla.netfilter.org/show_bug.cgi?id=1436 Bug ID: 1436 Summary: nf_conntrack_update fails in fedora kernels 5.6.16 and 5.6.18 Product: netfilter/iptables Version: linux-2.6.x Hardware: x86_64 OS: Fedora Status: NEW Severity: critical Priority: P5 Component:

On Thu, 2019-12-26 at 09:00 +0100, daggs wrote: > Greetings, > > I'm trying to bring up a alpine rpi aarch64 image within kvm but I'm ended up with a stuck system, here is the xml: [...] > generated using this cmd: > virt-install --cpu cortex-a53 --name alpine_rpi4_dev_machine --cdrom ./alpine-virt-3.11.2-aarch64.iso --disk path=alpine-rpi4.qcow2,size=8 --vcpus 4 --memory

On Mon, 2020-01-06 at 20:31 +0100, daggs wrote: > > > I'm using ubuntu 16.04 with libvirt 1.3.1, if this is a version issue, I can upgrade to latest version. > > > what I'm I missing? > > > > Your version of libvirt (as well as QEMU and virt-manager, I assume) > > is fairly old, and aarch64 support specifically has seen quite a few > >

Greetings Andrea, > Sent: Monday, January 06, 2020 at 11:37 AM > From: "Andrea Bolognani" <abologna@redhat.com> > To: daggs <daggs@gmx.com>, libvirt-users@redhat.com > Subject: Re: [libvirt-users] aarch64 vm doesn't boots > > On Thu, 2019-12-26 at 09:00 +0100, daggs wrote: > > Greetings, > > > > I'm trying to bring up a alpine rpi

On Mon, Jan 13, 2020 at 01:42:24AM +0100, Oliver Dzombic wrote: > Hi, > > i am running: > > libvirt-5.6.0-5.fc31.x86_64 > 5.4.8-200.fc31.x86_64 > > > Using: > > <blkiotune> > <device> > <path>/dev/sda1</path> > <read_iops_sec>100</read_iops_sec> >

On Thu, Apr 02, 2020 at 08:47:30AM +0800, FuLong Wang wrote: > Hello Experts, > > > Do we have libvirt source rpms (version above 5.9.0) for CentOS or RHEL? > > I only find source rpms for fedora in below public link. > > https://libvirt.org/sources/ Please ignore all the RPMs you see there, they really shouldn't be used. The source tarballs (eg

SELinux is preventing 11-dhclient from add_name access on the directory chrony.servers.wlp8s0. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that 11-dhclient should be allowed add_name access on the chrony.servers.wlp8s0 directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow

On Tue, 12 Nov 2019 09:22:56 +0200 Aki Tuomi via dovecot wrote: > Hi! > > Can you try follow this guide to get a core dump > > https://www.dovecot.org/bugreport-mail > > then provide > > > gdb /usr/lib/dovecot/auth /path/to/core > > bt full Sorry, I'm not familiar with gdb and can only provide this # gdb /usr/local/dovecot//libexec/dovecot/auth GNU

Wolfgang, (cc Linux XFS list) (cc Samba list) Quoting wolfgang.glas@ev-i.at: > I just found you message in the samba mailing list archives and foiund > out, that we have a very similar problem. We are using samba-2.2.1a on a > kerenl-2.4.16 and we use reiserfs. > We also experience data corruption with messages like: > > [2002/03/14 15:15:26, 0] >

Hello, I have a question regarding to access permissions. Recently I have upgraded my DC from version 41.12 to 4.1.21. This weekend I have decided to upgrade to 4.3.3. I have noticed that my users weren't able to access the sysvol share after the upgraded to 4.3.3. As a test I have created a new user "test" and I was able to open the sysvol share without any issues. Next I have

Hello, we have a Samba 3.2.8 msdfs root server. From time to time the connection from a Windows 2003 SP2 system will fail with the message that the server name could not be found. On Windows XP it seems to work. On Windows we open the folder user1/folder/subfolder with the explorer. In the failure log I can't see anything about the subfolder. If I compare the samba log (debug level 10)

I have a reproducible intermittent error large site - "The specified network name is no longer available". This happens when copying large files. Below is part of log level 10 output & strace. Sorry for the long posting. I will probably need to put the loglevel 10 attached to a bugzilla - but thought I would try the lists initially. RHEL4 samba-3.0.25b-1.el4_6.4

Hi, I'm facing an issue with at least two Samba servers in production both showing important number of log entries like: smbd[27355]: PANIC: assert failed at smbd/oplock.c(149): exclusive_oplocks_open>=0 Looking at the source code, this panic is triggered when the number of exclusive oplocks for a given file becomes negative. Once triggered for one smbd process, this process can

https://bugs.freedesktop.org/show_bug.cgi?id=111940 Bug ID: 111940 Summary: frequent timeout warnings during normal operation Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: not set Component: Driver/nouveau