similar to: O_EXCL unreliable?

Hi there, I was wondering if someone can assist with clarifying why O_EXCL does not always work with NFS. Is it related to NFS protocol version support or export permissions mode out of the Celerra/Netapp ( e.g: mixed mode, unix file permissions ? ) Please advise. Thanks. Regards, new dovecot user.

Hi Slight problem - linux 2.4 running dovecot, Solaris 2.8 home directory server. Full lockd support etc. I had to make the following code patches (at end of mail for clarity) to get dovecot to read the users mbox files at all. 1) fcntl with F_SETLKW will not work against a Solaris 2.8 server as proved with a small test program. Other forms of fcntl (ie F_SETLK) are OK. I noticed there are

Anyone who has NFS, could you test: http://dovecot.org/tmp/locktest.c 1. Compile: gcc locktest.c -o locktest -Wall -g 2. Start in server 1: ./locktest temp1 3. Start in server 2: ./locktest temp2 4. Server 1 might log "unlink() failed" error after starting the second locktest, ignore that. It starts writing something like: 1 successes 12 successes link() succeeded, but link count=1 12

Hi, I''d like to mark locally generated packets in the OUTPUT chain and do policy based routing (selecting one of two default gateways) based on the mark value. But when the packet hits the OUTPUT chain (in ''mangle'' table), the routing decision seems to be already made. AFAIK, locally generated packets do not pass the PREROUTING chain (so trying to mark them there

I have attached a patch that supports a new "--direct-write" option. The result of using this option is to write directly to the destination files, instead of a temporary file first. The reason this patch is needed is for rsyncing to a device where the device is full or nearly full. Say that I am writing to a device that has 1 Meg free, and a 2 meg file on that device is out of date.

Today, rsyncd manages its pid file by open()ing it with O_CREAT|O_EXCL at startup, and then unlink()ing it at shutdown. If the open() fails at startup because the file already exists, then rsyncd will assume another instance of itself is already running and not start. However, there's a problem with this approach: if rsyncd is terminated without being able to clean up (e.g., kill -9, or the

Hello, when I do: /opt/rsync/bin/rsync /etc/hosts targethost::bkp/ I get: cannot create .hosts.b0WX1x : File exists I check the targethost and I get empty file .hosts.b0WX1x When trying with other targethost-s it works, but on this one it doesn't. On the other targethosts I have exactly the same LinuX distribution, permissions and users than on the problem targethost. I have exactly the

Hi, on AIX, mkstemp doesn't open a file with the O_LARGEFILE option, so you can't transfer files > 2GB to an AIX machine. Here is a fix: diff -c -r rsync-2.5.6.orig/syscall.c rsync-2.5.6/syscall.c *** rsync-2.5.6.orig/syscall.c Sun Jan 26 21:09:02 2003 --- rsync-2.5.6/syscall.c Wed May 14 13:55:15 2003 *************** *** 151,157 **** if (dry_run) return -1; if

Hi, I need to to open existing readonly files. Yes you are right, not the open call takes the time, but stat() system call. I looked at aio_pthread source, the lines which needs to be removed to make it work are just the lines which tests for O_CREAT|O_EXCL? What problems can cause such solution for readonly share? On Tue, Apr 26, 2016 at 8:42 PM, Jeremy Allison <jra at samba.org> wrote:

On 10/27/2014 02:02 PM, Konrad Rzeszutek Wilk wrote: > On Mon, Oct 27, 2014 at 01:38:20PM -0400, Waiman Long wrote: >> >> My concern is that spin_unlock() can be called in many places, including >> loadable kernel modules. Can the paravirt_patch_ident_32() function able to >> patch all of them in reasonable time? How about a kernel module loaded later >> at run

On 10/27/2014 02:02 PM, Konrad Rzeszutek Wilk wrote: > On Mon, Oct 27, 2014 at 01:38:20PM -0400, Waiman Long wrote: >> >> My concern is that spin_unlock() can be called in many places, including >> loadable kernel modules. Can the paravirt_patch_ident_32() function able to >> patch all of them in reasonable time? How about a kernel module loaded later >> at run

Dear List, I'm trying to get diff/removed data and it's offset out. So I write a functions in receive_data. When I run backup, I found there is a weird behavior which I don't understand. i = recv_token(f_in, &data) will receive (i = -1, offset2 = 0) some where in the middle of the transfer procedure. That's to say, it's going to transfer the first data block from sender,

The /dev/[r]dsk nodes implement the O_EXCL flag. If a node is opened using the O_EXCL, subsequent open(2) to that node fail. But I dont think the same is true for /dev/zvol/[r]dsk nodes. Is that a bug (or maybe RFE) ? Thanks Sumit -- This messages posted from opensolaris.org

I found something interesting via strace. lda is writing a timestamp with utime before doign the fsync, but I'm really not a C guy, so I have no idea why that's going on via procmail and not via commandline. I assume it's related to the choice of pread64 vs read. when called from commandline (working): read(0, "July 14-20, 2013\n10 courses. Bon"..., 4096) = 4096

I removed the O_CREAT|O_EXCL checks and added check to exclude O_DIRECTORY, but it is not working, opening of files fails and I don't know why. I can see in strace logs that openat syscall in vfs_aio_pthread was successful, but it still fails and this messages are logged: [2016/04/28 13:28:59.691782, 5, pid=5623, effective(32697, 10513), real(32697, 0)]

While doing migration, sometimes found suspend lock file was not unlinked in previous operations, then there is an obsolete lock file in place, which causes the current and later migration cannot get lock. That happens seldomly but do happen. After checking the source code, I found there are some places that potentially cause lock file unlinked, including: 1) in lock_suspend_event() function,

We should avoid using non multi-path (mp) path for mp disks As of now there is no good way (like api) to check that. A workaround way is to check if the O_EXCL open is unsuccessful. This is safe since otherwise the BTRFS_IOC_SCAN_DEV ioctl would fail if the disk-path can not be opened with the flag O_EXCL set. This patch also includes some (error) print format changes related to the btrfs

Hi everybody, I know this has been discussed ad naseum, but I can't find an answer to my question precisely. My version of samba is 4.2.10. Here's my question. I have POSIX ACLs set on a directory like this: # file: . # owner: root # group: admin # flags: -s- user::rwx user:apache:rwx group::rwx group:admin:rwx mask::rwx other::r-x default:user::rwx default:user:apache:rwx

I am trying to see if Samba 4.2.0rc4 will run on a Solaris 10 i386 system. After getting it to build, startup fails. Starting it up as smbd -i -d 10 The output indicates that everything is starting normally until the following is output: messaging_dgm_lockfile_create: ftruncate failed: Invalid argument messaging_dgm_init: messaging_dgm_create_lockfile failed: Invalid argument messaging_dgm_init

I added debuging as follows: /* no O_EXCL, existence check is via the fcntl lock */ lockfile_fd = open(lockfile_name.buf, O_NONBLOCK|O_CREAT|O_WRONLY, 0644); if (lockfile_fd == -1) { ret = errno; DEBUG(1, ("%s: open failed: %s\n", __func__, strerror(errno))); return ret; }