similar to: smb locks

Hello, I'm using the Samba server 3.0.33 that exports volume from a GPFS. The GPFS strongly dislikes unlinking files that are locked (resulting in permission denied) using fcntl F_SETLEASE. It seems that the Samba *sometimes* tries to unlink a file that is oplocked. Why? Is this a bug? Why it does not happen always but only sometimes? I have strace logs showing: Wrong case: 8711

Dear all, > Caveats > ======= > Features which OCFS2 does not support yet: > - extended attributes > - readonly mount > - shared writeable mmap > - loopback is supported, but data written will not > be cluster coherent. > - quotas > - cluster aware flock <---------------------------------------- >

Hi list We recently upgraded our fileservers from Centos supplied 4.2.10 to Sernet 4.4.6, and then our DCs from 3.6.x to 4.4.6. It seems that since then we've had problems with locks not being obeyed on all nodes - they only seem to work when a second client opens a file on the same node as the first client. For example, when a user opens an Excel file I will see something like this

Can anyone help with some pointers to debug a problem with Samba and CTDB with smbstatus traversing the connections tdb? I've got a new two node cluster with Samba and CTDB on AIX. If I run smbstatus when the server has much user activity it hangs and the node it was run on gets banned. I see the following in the ctdb log: 2014/10/29 11:12:45.374580 [3932342]:

Hello, maybe there is someone they can help and answer a question why i get these network screen on my ctdb clusters. I have two ctdb clusters. One physical and one in a vmware enviroment. So when i transfer any files (copy) in a samba share so i get such network curves with performance breaks. I dont see that the transfer will stop but why is that so? can i change anything or does anybody know

On Thu, Jul 14, 2016 at 02:22:12PM +0100, Alex Crow wrote: > At the moment we're pretty happy with the Samba side of things. I > did wonder if there was any help that you kind chaps might be able > to give to the MooseFS guys if they need it (they've not asked yet > but I've suggested they might be able to). Overall it's working The main hint I would like to give to

On Thu, Jul 14, 2016 at 02:39:48PM +0100, Alex Crow wrote: > >The main hint I would like to give to the MooseFS developers is to get > >ping_pong -rw working. If you need any assistance in setting that up > >and getting arguments on why this is important, let us know! > > > >With best regards, > > > >Volker > > Any arguments that I can pass on would

On 03/11/16 14:28, Ralph Böhme wrote: > >> Ah, my smb.conf is missing the "ctdb socket" parameter. According to "man >> smb.conf" this should be set, but I don't remember seeing it on the wiki >> pages. > if it's not set, the default is used which works in many cases, but > not in mine. If the default wasn't working in your setup,

Hi, This morning our CTDB managed cluster took a nosedive. We had member machines with hung smbd tasks which causes them to reboot, and the cluster did not come back up consistently. We eventually got it more or less stable with two nodes out of the 3, but we're still seeing worrying messages, eg we've just noticed: 2017/04/19 12:10:31.168891 [ 5417]: Vacuuming child process timed

mainly question for the intel folks, any chance to rerun the ltp testsuites to see how we are doing these days with all the changes ? thanks :) Wim

Hi - I'm trying to verify if OpenSSH/SFTP will in fact lock files with advisory file locking in Linux. I can test locking with the linux "flock" command to verify that file locking does work - but when I upload or download a file with SFTP it will not detect a lock. I'm asking about Linux specifically because about a year ago I was doing a similar process in Solaris 9 and

Hello all, First of all, apologies if this isn't the right location for this question, I couldn't find a CTDB specific mailing list or IRC so I figured the general one would be appropriate. Please let me know if this question is better placed elsewhere. I'm trying to test clustered samba and have a two node CTDB setup (Following the guide here:

Hi Volker and many thanks for your response According to your questions >Please remove the SO_RCVBUF and SO_SNDBUF entries. >Oh, that's ancient. Do you have any possibility to move to >"security=user"? The smb.conf file was inherited from HP-UX system. Ok, I'll remove them >Did you try "posix locking = no"? That is mostly criticial >if

On 03/11/16 13:12, Ralph Böhme wrote: > >> Hi there, >> >> Can you send your smb.conf so I can compare it to mine? > sure. It's a virtual cluster in LXC containers with 3 nodes, > filesystem is a bind mount with ext4. > > # cat /var/lib/lxc/ctdb-node0/rootfs/opt/samba/etc/smb.conf > [global] > clustering = yes > ctdbd socket =

(Samba 3.0.21c / kernel 2.4.27 / Debian Sarge) Hello, One of my user open a file (located on a SAMBA server) in its application, and when he tries to save it, he gets a "share violation" error. (other people have this problem too). This error happens since I upgraded the SAMBA server from 3.0.14a to 3.0.21c. smbstatus for this file: 32613 DENY_WRITE 0x20089 RDONLY

[2799/3801] Compiling source3/locking/locking.c [2800/3801] Compiling source3/locking/brlock.c ../source3/locking/brlock.c: In function 'brl_get_locks_readonly_parser': ../source3/locking/brlock.c:2071: error: expected expression before 'struct' ../source3/locking/brlock.c:2071: warning: assignment makes pointer from integer without a cast ../source3/locking/brlock.c: In function

On Tue, Dec 16, 2014 at 03:40:08PM +0100, Nacho del Rey wrote: > Hi there > > In an Oracle RAC cluster using ACFS (as file-system) where we have a samba > server for sharing files to windows clients, we are suffering a strange > issue, from time to time, which it causes the Windows clients lock for a > while (10 min or a bit more) or even indefinitely when they are working >

I was testing ocfs2 on a 2 node cluster set up. ocfs2-tools version is 1.6.3 ocfs2 kernel version is 2.6.36 Using cman on 2 nodes node02 dw # ping_pong -rwm /data/test.dat 3 data increment = 2 14 locks/sec node01 dw # ping_pong -rw /data/test.dat 3 data increment = 2 10 locks/sec node02 dw # ping_pong -r /data/test.dat 3 1980 locks/sec Using cman on 1 node node02 dw #

When using Samba 3.0.23b (slightly old, I know) on CentOS 4.4, smbstatus -B fails with a segmentation fault. smbstatus works, and tdbdump is able to dump brlock.tdb and locking.tdb without any errors (which is not what I expected). Here's the backtrace (non-ASCII characters replaced with 'X'): #0 0x0017fa2c in memcpy () from /lib/tls/libc.so.6 #1 0x0029b19f in tdb_write

On Tue, Apr 22, 2014 at 11:11:50AM +0800, Jason Wang wrote: > On 04/21/2014 11:11 PM, Amos Kong wrote: > > Currently ethtool returns zero if there is no virtqueue or MQ isn't > > support, we should return -ENOTSUPP to notice user. > > > > Signed-off-by: Amos Kong <akong at redhat.com> > > --- > > drivers/net/virtio_net.c | 2 +- > > 1 file