search for: fdatasync

Hi. In ocfs2, fdatasync and fsync are identical. I think fdatasync should skip committing transaction when inode->i_state is set just I_DIRTY_SYNC and this indicates only atime or/and mtime updates. Following patch improves fdatasync throughput. #sysbench --num-threads=16 --max-requests=300000 --test=fileio --file-b...

Hi. In btrfs, fdatasync and fsync are identical. I think fdatasync should skip committing transaction when inode->i_state is set just I_DIRTY_SYNC and this indicates only atime or/and mtime updates. Following patch improves fdatasync throughput. #sysbench --num-threads=16 --max-requests=10000 --test=fileio --file-bl...

Hello, We found that fsync and fdatasync syscalls sometimes don't sync data in an ext3 file system under the following conditions. 1. Kernel version is 2.6.6 or later (including 2.6.8.1 and 2.6.9-rc2). 2. Ext3's journalling mode is "data=journal". 3. Create a file (whose size is 1Mbytes) and execute umount/mount. 4. lse...

My application always needs to sync file data after writing. I don't want anything handing around in the kernel buffers. I am wondering what is the best method to accomplish this. 1. Do I use EXT2 and use fdatasync() or fsync()? 2. Do I use EXT2 and mount with the "sync" option? 3. Do I use EXT2 and use the O_DIRECT flag on open()? 4. Do I use EXT3 in full journaled mode, where the data and metadata are journaled? In this case, is the journaled data sync'd or async'd? When the journ...

Linux kernel (as of 2.6.15.4) has the following performance bug: Syncing (fsync() or fdatasync()) files with zero links (deleted files) in not no-op, as it should be. See details, a test C program, and the rationale in the URL below: http://b2e.ex-code.com/index.php/soft/2006/02/24/linux_performance_bug_zero_links_fsync In the article with the URL above it is also explained how to make mu...

Hello list, I have a dovecot 2.2.5 instance configured to use mdbox as mailbox format. I configured to use separate storage attachments and use SIS.. (doveconf -n below) I get this error Sep 6 12:29:52 vrajah.mydomain.tld dovecot: lmtp(14258, email at mydomain.tld): Error: fdatasync(/apps/mail/mailbox/attachments/23/12/2312039008db057a1c75-2efc2d00687d2952b2370000f89409f1) failed: Bad file descriptor I'm using centos 6.4 on a KVM with ext4 as fs. Can someone tell me why i'm getting this error? and how to fix this? -Thanks in advance Vijay ##########doveconf -n #...

...n the past[1] to use the fadvise interface, but kernel limitations have made this quite messy. In particular, the kernel supports FADV_DONTNEED as a single-shot hint; i.e. if the page is clean when the hint is given it will be freed, otherwise the hint is ignored. For this reason it is necessary to fdatasync() against dirtied pages before giving the hint. This, however, requires that rsync do some accounting, calling fdatasync() and fadvise() only after giving the kernel an opportunity to flush the data itself. Moreover, fadvise(DONTNEED) frees pages regardless of whether the hinting process is the on...

...nclude "isaligned.h" @@ -263,9 +265,30 @@ file_can_trim (void *handle) #endif } +static int +file_can_fua (void *handle) +{ + return NBDKIT_FUA_NATIVE; +} + +/* Flush the file to disk. */ +static int +file_flush (void *handle, uint32_t flags) +{ + struct handle *h = handle; + + if (fdatasync (h->fd) == -1) { + nbdkit_error ("fdatasync: %m"); + return -1; + } + + return 0; +} + /* Read data from the file. */ static int -file_pread (void *handle, void *buf, uint32_t count, uint64_t offset) +file_pread (void *handle, void *buf, uint32_t count, uint64_t offset, +...

...issue after rebalanced volume. Crash stack bellow: +------------------------------------------------------------------------------+ pending frames: patchset: git://git.gluster.com/glusterfs.git signal received: 11 time of crash: 2013-03-14 16:33:50 configuration details: argp 1 backtrace 1 dlfcn 1 fdatasync 1 libpthread 1 llistxattr 1 setfsid 1 spinlock 1 epoll.h 1 xattr.h 1 st_atim.tv_nsec 1 package-string: glusterfs 3.3.0 /lib64/libc.so.6[0x38d0a32920] /lib64/libc.so.6(memcpy+0x309)[0x38d0a88da9] /usr/sbin/glusterfs(mgmt_getspec_cbk+0x398)[0x40c888] /usr/lib64/libgfrpc.so.0(rpc_clnt_handle_reply+0xa...

...Linux linux-7lbv 2.6.27.19-5-pae #1 SMP 2009-02-28 04:40:21 +0100 i686 i686 i386 GNU/Linux $ gem install sqlite3-ruby Building native extensions. This could take a while... ERROR: Error installing sqlite3-ruby: ERROR: Failed to build gem native extension. /usr/bin/ruby extconf.rb checking for fdatasync() in -lrt... yes checking for sqlite3.h... no make make: *** No rule to make target `ruby.h'', needed by `sqlite3_api_wrap.o''. Stop. Gem files will remain installed in /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4 for inspection. Results logged to /usr/lib/ruby/gems/1.8/gems/s...

...lloc.o zalloc.o calloc.o \ mmap.o shm_open.o shm_unlink.o \ memcpy.o memcmp.o memset.o memccpy.o memmem.o memswap.o \ diff --git a/usr/klibc/SYSCALLS.def b/usr/klibc/SYSCALLS.def index 41cfa17..c56e8f9 100644 --- a/usr/klibc/SYSCALLS.def +++ b/usr/klibc/SYSCALLS.def @@ -189,8 +189,10 @@ int fdatasync,fsync::fdatasync(int); int readv(int, const struct iovec *, int); int writev(int, const struct iovec *, int); int ftruncate64,ftruncate::ftruncate(int, off_t); -ssize_t pread64,pread::pread(int, void *, size_t, off_t); -ssize_t pwrite64,pwrite::pwrite(int, void *, size_t, off_t); +<parisc>...

...wn flag (0x%x)", flags); > + *error = EINVAL; > + return 0; > + } Right now, our NBD_CMD_FLAG_FUA implementation causes a full flush action from the plugin, even if it is possible to write a client that knows how to preserve FUA semantics in a lighter-weight manner than a full fdatasync(). In other words, it obeys the semantics required by the NBD protocol, but not necessarily in the most optimum way. Unfortunately, the callback interfaces for a plugin do not have any way to pass flags from the client to the plugin (other than my new .zero callback, but right now it only support...

...t rustcorp.com.au> diff --git a/Documentation/lguest/lguest.c b/Documentation/lguest/lguest.c --- a/Documentation/lguest/lguest.c +++ b/Documentation/lguest/lguest.c @@ -1630,6 +1630,13 @@ static bool service_io(struct device *de } } + /* OK, so we noted that it was pretty poor to use an fdatasync as a + * barrier. But Christoph Hellwig points out that we need a sync + * *afterwards* as well: "Barriers specify no reordering to the front + * or the back." And Jens Axboe confirmed it, so here we are: */ + if (out->type & VIRTIO_BLK_T_BARRIER) + fdatasync(vblk->fd); +...

Linus, et al, Here are the ocfs2 updates for 2.6.31. It's a quiet cycle, almost completely composed of fixes. There is a nice performance improvement from Hisashi Hifumi for fdatasync. Please pull. Joel The following changes since commit b4348f32dae3cb6eb4bc21c7ed8f76c0b11e9d6a: Linus Torvalds (1): Merge branch 'for-linus' of git://oss.sgi.com/xfs/xfs are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/jlbec/ocfs2.git u...

.... Since it happens quite seldom, there must be other conditions or circumstances that have to be met for the problem to occur. Unfortunately I don't know which. Shortly after the mail gets delivered on server2, I get the following errors on server1: mail01 dovecot: IMAP(akzidenz at triner.ch): fdatasync(/data/vmail/example.com/user/dovecot-uidlist) failed: Input/output error mail01 dovecot: IMAP(akzidenz at triner.ch): /data/vmail/example.com/user/dovecot-uidlist: next_uid was lowered (2143 -> 2142, hdr=2142) The new mail is than missing in the uidlist and as long as no new mail arrives all fo...

...t rustcorp.com.au> diff --git a/Documentation/lguest/lguest.c b/Documentation/lguest/lguest.c --- a/Documentation/lguest/lguest.c +++ b/Documentation/lguest/lguest.c @@ -1630,6 +1630,13 @@ static bool service_io(struct device *de } } + /* OK, so we noted that it was pretty poor to use an fdatasync as a + * barrier. But Christoph Hellwig points out that we need a sync + * *afterwards* as well: "Barriers specify no reordering to the front + * or the back." And Jens Axboe confirmed it, so here we are: */ + if (out->type & VIRTIO_BLK_T_BARRIER) + fdatasync(vblk->fd); +...

So Richard recently blogged about running many libguestfs mounts in parallel. I actually want parallelization in the other way; I use guestmount to access a disk image, and my program is multithreaded. It does read/write and most especially calls to link() and fdatasync() from threads. However, this all ends up being serialized, because the guestfsd protocol is synchronous, and the daemon side is single-threaded. Related to this, the qemu instance is always booted with only one vCPU. Have there been any thoughts on fixing this?

This patch optimizes the tree logging stuff so it doesn''t always wait 1 jiffie for new people to join the logging transaction if there is only ever 1 writer. This helps a little bit with latency where we have something like RPM where it will fdatasync every file it writes, and so waiting the 1 jiffie for every fdatasync really starts to add up. Signed-off-by: Josef Bacik <jbacik@redhat.com> --- fs/btrfs/ctree.h | 2 ++ fs/btrfs/tree-log.c | 12 +++++++++++- 2 files changed, 13 insertions(+), 1 deletions(-) diff --git a/fs/btrfs/...

...: % time seconds usecs/call calls errors syscall ------ ----------- ----------- --------- --------- ---------------- 97.18 19.592537 1878 10430 munmap 2.28 0.458984 36 12696 epoll_ctl 0.26 0.052926 10 5288 fdatasync 0.21 0.042472 3 13679 epoll_wait ... snip ... Why would that happen? (dovecot 2.1.17) -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstra?e 15, 81669 M?nchen Sitz der Gesellschaft: M?nchen, Amtsgericht M?nchen: HRB 199263 Vorstand: Patrick Be...

...ruby-sqlite3 via gem, but it keeps givin' me this output: mathilda ~ # gem install sqlite3-ruby Building native extensions. This could take a while... ERROR: Error installing sqlite3-ruby: ERROR: Failed to build gem native extension. /usr/bin/ruby extconf.rb install sqlite3-ruby checking for fdatasync() in -lrt... no checking for sqlite3.h... no make make: *** No rule to make target `ruby.h', needed by `sqlite3_api_wrap.o'. Stop. Gem files will remain installed in /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-1.2.4 for inspection. Results logged to /usr/lib/ruby/gems/1.8/gems/sqlite3-ruby-...