SYNC(2) Linux Programmer's Manual SYNC(2)NAME
sync - commit buffer cache to disk
SYNOPSIS
#include <unistd.h>
void sync(void);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
sync():
_BSD_SOURCE || _XOPEN_SOURCE >= 500 || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED
DESCRIPTION
sync() first commits inodes to buffers, and then buffers to disk.
ERRORS
This function is always successful.
CONFORMING TO
SVr4, 4.3BSD, POSIX.1-2001.
NOTES
Since glibc 2.2.2 the Linux prototype is as listed above, following the various standards. In libc4, libc5, and glibc up to 2.2.1 it was
"int sync(void)", and sync() always returned 0.
BUGS
According to the standard specification (e.g., POSIX.1-2001), sync() schedules the writes, but may return before the actual writing is
done. However, since version 1.3.20 Linux does actually wait. (This still does not guarantee data integrity: modern disks have large
caches.)
SEE ALSO bdflush(2), fdatasync(2), fsync(2), sync(8), update(8)COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2010-09-20 SYNC(2)
Check Out this Related Man Page
SYNC(2) Linux Programmer's Manual SYNC(2)NAME
sync, syncfs - commit buffer cache to disk
SYNOPSIS
#include <unistd.h>
void sync(void);
int syncfs(int fd);
Feature Test Macro Requirements for glibc (see feature_test_macros(7)):
sync():
_BSD_SOURCE || _XOPEN_SOURCE >= 500 || _XOPEN_SOURCE && _XOPEN_SOURCE_EXTENDED
syncfs():
_GNU_SOURCE
DESCRIPTION
sync() causes all buffered modifications to file metadata and data to be written to the underlying file systems.
syncfs() is like sync(), but synchronizes just the file system containing file referred to by the open file descriptor fd.
RETURN VALUE
syncfs() returns 0 on success; on error, it returns -1 and sets errno to indicate the error.
ERRORS
sync() is always successful.
syncfs() can fail for at least the following reason:
EBADF fd is not a valid file descriptor.
VERSIONS
syncfs() first appeared in Linux 2.6.39; library support was added to glibc in version 2.14.
CONFORMING TO
sync(): SVr4, 4.3BSD, POSIX.1-2001.
syncfs() is Linux-specific.
NOTES
Since glibc 2.2.2 the Linux prototype for sync() is as listed above, following the various standards. In libc4, libc5, and glibc up to
2.2.1 it was "int sync(void)", and sync() always returned 0.
BUGS
According to the standard specification (e.g., POSIX.1-2001), sync() schedules the writes, but may return before the actual writing is
done. However, since version 1.3.20 Linux does actually wait. (This still does not guarantee data integrity: modern disks have large
caches.)
SEE ALSO bdflush(2), fdatasync(2), fsync(2), sync(8), update(8)COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2012-05-04 SYNC(2)
Hi,
I want to remove a directory recursively except the inside directories calles .SYNC (designsync dirs) I am looking for something like:
\rm -rf < find . * | grep -v .SYNC
The find works ok but I do not know how to redirect it.
Please help.
Regards,
Ziv:rolleyes: (1 Reply)
Hi,
I want to remove a directory recursively except the inside directories calles .SYNC (designsync dirs) I am looking for something like:
\rm -rf < find . * | grep -v .SYNC
The find works ok but I do not know how to redirect it.
Please help.
Regards,
Ziv (3 Replies)
Anyone know how to go about skipping the initial disk sync of a newly created drbd resource?
I'm creating brand new 30gb partitions and would like to skip the entire initial sync, I've read this is possible but I cannot seem to find the instructions to do it.
Thanks,
Trey (2 Replies)
Hello friends,
I am new on linux, i am facing issues on below script.
#!/bin/sh
current=1355147377
echo $current
last_modified=1354537347
echo $last_modified
DIFF='expr ($current - $last_modified)'
echo $DIFF
Please view this code tag video for how to use code tags when posting... (8 Replies)