search for: syncf

...5PM +0200, Bodo Thiesen wrote: > > Since it never get's updated unless the file system is unmounted, it can > only be used for a 24 hours test by mounting the file system now, > unmounting it 24 hours from now and then taking the difference. It also gets updated if the file system syncfs(2) or sync(2) system call. But if you crash, any writes since the last syncfs(2), sync(2), or umount(2) call on the file system can get lost, yes. > Also the value is only available in granularity of 1 GB (plus minus > 512MB) - at least in my case. This is what dumpe2fs is currently using...

* Andreas Dilger <adilger@dilger.ca> hat geschrieben: > The "lifetime writes" value has not been around forever, so if the > filesystem was originally created and populated on an older kernel > (e.g. using ext3) it would not contain a record of those writes. It was created as stable ext4 in the first place. So only if there was a stable ext4 release which didn't

.../main.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/extlinux/main.c b/extlinux/main.c index 0204caa..f7eeeb7 100644 --- a/extlinux/main.c +++ b/extlinux/main.c @@ -687,6 +687,8 @@ static int xfs_install_file(const char *path, int devfd, struct stat *rst) } close(dirfd); + + syncfs(fd); close(fd); return 0; -- 1.8.1

Hello, since we are using rsync for backing up millions of files in a virtual environment, and most of the virtual machines run on SSD cached storage, i`d be curious how that negatively impacts lifetime of the SSD`s when we do rsync run every night for backup my question: does rsync normal file comparison run to determine if anything has changed change atime of any files ? for me it seems,

I believe 30 sec is the default for the checkpoint interval.  Is this adjustable? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

...newselect SYSCALL FOUND: spu_create SYSCALL FOUND: setns SYSCALL FOUND: fgetxattr SYSCALL FOUND: fchmod SYSCALL FOUND: timer_settime SYSCALL FOUND: oldolduname SYSCALL FOUND: sync SYSCALL FOUND: setsockopt SYSCALL FOUND: socket SYSCALL FOUND: fanotify_mark SYSCALL FOUND: finit_module SYSCALL FOUND: syncfs SYSCALL FOUND: setsid SYSCALL FOUND: prof SYSCALL FOUND: subpage_prot SYSCALL FOUND: setfsgid SYSCALL FOUND: epoll_create SYSCALL FOUND: epoll_wait SYSCALL FOUND: tgkill SYSCALL FOUND: flock SYSCALL FOUND: capget SYSCALL FOUND: sethostname SYSCALL FOUND: getpid SYSCALL FOUND: add_key SYSCALL FOUND...

On Tue, Aug 20, 2013 at 07:44:39AM +0200, leroy christophe wrote: > > > Find attached two patches I have in order to build klibc 2.0.2 > against kernel 3.8.13 > We had to introduce those patches when going from kernel 3.6 to kernel 3.7 > Hope it helps. > those patches are wrong and again very brittle. just use the way it is described in `make help': A) cd ~/src/linux