search for: o_noatime

...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, stat/lstat calls of rsync do NOT modify atime, but i`m not sure under which conditions atime is changed. grepping the source for O_NOATIME in rsync3.txt i found : - Propagate atimes and do not modify them. This is very ugly on Unix. It might be better to try to add O_NOATIME to kernels, and call that. furhermore, apparently there _IS_ O_NOATIME in linux kernels for a while: http://man7.org/linux/man-pages/man2/open.2.ht...

Hi there, At the Tracker project we use FLAC__metadata_simple_iterator_init to extract metadata from FLAC files. Although this API has a boolean that restores the stat results of the file after iteration, it's still not the same as passing O_NOATIME. Ideally we can pass a int fd instead of a filename, and doesn't the metadata iterator try to write to the fd at all. Then we can open() a fd with O_NOATIME ourselves. Regards, Philip -- Philip Van Hoof freelance software developer Codeminded BVBA - http://codeminded.be

On Wed 26 Oct 2016, devzero at web.de wrote: > > 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

https://bugzilla.samba.org/show_bug.cgi?id=7249 Summary: Add an option to use O_NOATIME Product: rsync Version: 3.1.0 Platform: Other OS/Version: Linux Status: NEW Severity: enhancement Priority: P3 Component: core AssignedTo: wayned at samba.org ReportedBy: nicolas.george at normalesup.or...

Hi I have a single filesystem i don't mount noatime because mutt would work very good otherwise. Today, in a discussion about mkisofs, i learned that Linux since 2.6.8 supports "O_NOATIME" as an option to open. (see "man 2 open") So how comes that rsync doesn't do that and/or there is no option to switch on that behaviour? Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in...

...brief pause (few seconds), and then you mount and back up the snapshot for a fully consistent database (only way to do that other than freezing all writes during a mysqldump, which can take a long time for larger DBs). That also avoids the access-time churn (for backup programs that don't know O_NOATIME, like any that use rsync). That's server stuff. On a desktop with a combination of SSD and "spinning rust" drives, LVM can give you transparent SSD caching of "hot" data (rather than you having to put some filesystems on SSD and some on hard drive). Now, if btrfs ever get...

Hey everyone, I am a final semester MCA student. I've chosen rsync as the subject of my project for my graduation. Hence I would appreciate it if someone could guide me with some ideas on how I can contribute to rsync. I will work hard to implement whatever suggestions that you can all give me. I would definitely like to know what are some of the issues concerning rsync. May be I can then

...010 #define O_NONBLOCK 0x0080 #define O_CREAT 0x0100 #define O_TRUNC 0x0200 @@ -27,11 +26,14 @@ #define O_NOCTTY 0x0800 #define FASYNC 0x1000 #define O_LARGEFILE 0x2000 +#define O_SYNC 0x4010 #define O_DIRECT 0x8000 #define O_DIRECTORY 0x10000 #define O_NOFOLLOW 0x20000 #define O_NOATIME 0x40000 #define O_CLOEXEC 0x80000 +#define O_PATH 0x200000 +#define O_TMPFILE 0x410000 #define O_NDELAY O_NONBLOCK @@ -53,6 +55,24 @@ #define F_SETLK64 34 #define F_SETLKW64 35 +#define F_SETOWN_EX 15 +#define F_GETOWN_EX 16 + +#define F_GETOWNER_UIDS 17 + +#define F_OFD_GETLK 36 +#defin...

...ore common and more consistent: https://bitbucket.org/gordonmessmer/dragonsdawn-snapshot If you're interested in testing or development (or even advocacy), I'd love to have more people contributing. > That also avoids the access-time churn (for backup programs that > don't know O_NOATIME, like any that use rsync). Yes, though rsync based systems are usually always-incremental, so they won't access files that haven't been modified, and impact on atime is minimal after the first backup. > That's server stuff. On a desktop with a combination of SSD and > "s...

Hello I am making backup of a Plesk Debian server to /backup using Rsync. My questioin is how can I preserve the ctime, mtime, and atime of original files? Thanks

Hi! I've just tried to do a backup of a machine with rsync. While doing this (I was reading emails:-) I noted that mbox for mbox, I had no longe new mails, but I've never read off these mailboxes lately... This seemed to be a st_atime problem, and indeed, I could verify that. This is what I used for backup: rsync --archive \ --recursive \

...7 @@ Desirable features: Alternatively, as long as transfers are idempotent, we can just restart the whole thing. [NFSv4] - - Scripting support. + - Scripting support. - Propagate atimes and do not modify them. This is very ugly on Unix. It might be better to try to add O_NOATIME to kernels, and @@ -224,7 +224,7 @@ Scripting hooks: - What basis file to use - Logging - + - Whether to allow transfers (for public servers) - Authentication @@ -275,7 +275,7 @@ Pie-in-the-sky features: These might have a severe impact on the protocol, and are not clearly...

...15 ++++++++++----- 2 files changed, 19 insertions(+), 7 deletions(-) diff --git a/cmds-receive.c b/cmds-receive.c index ed44107..cce37a7 100644 --- a/cmds-receive.c +++ b/cmds-receive.c @@ -257,8 +257,15 @@ static int process_snapshot(const char *path, const u8 *uuid, u64 ctransid, O_RDONLY | O_NOATIME); if (args_v2.fd < 0) { ret = -errno; - fprintf(stderr, "ERROR: open %s failed. %s\n", - parent_subvol->path, strerror(-ret)); + if (errno != ENOENT) + fprintf(stderr, "ERROR: open %s failed. %s\n", + parent_subvol->path, strerror(-ret)); + else + fpr...

Most fixes are trivial. The one from Alex is fixing a real bug that several users have reported. Alex sent the patch half a year ago and it was not yet integrated. The patch "Use /proc/mounts instead of /etc/mtab" is a repost. The patch "btrfs-receive optionally honors the end-cmd" is a preparation step to allow backup tools to multiplex a single communication stream (e.g. a

...;; + char tmp_dir[30] = "/tmp"; + char *full_path = NULL; ret = finish_subvol(r); if (ret < 0) @@ -253,13 +258,47 @@ static int process_snapshot(const char *path, const u8 *uuid, u64 ctransid, } }*/ - args_v2.fd = openat(r->mnt_fd, parent_subvol->path, - O_RDONLY | O_NOATIME); + ret = mnt_to_dev(r->root_path, &dev); + if (ret) + goto out; + if (!mktemp(tmp_name)) { + fprintf(stderr, "ERROR: fail to generate a tmp file\n"); + goto out; + } + strncat(tmp_dir, "/", 1); + strncat(tmp_dir, tmp_name, strlen(tmp_name)); + + ret = mkdir(tmp_dir, 0...

Bradley, and the rsync development team, I came across the following message on the rsync bug tracking system, while searching for just this feature (access time preservation)... http://rsync.samba.org/cgi-bin/rsync/incoming?id=2509;expression=atime;user=guest ... where it is written... > Date: Mon, 7 Feb 2000 02:59:42 -0500 > From: "Bradley M. Kuhn" <bkuhn@ebb.org> >

...txt --- rsync-2.6.6/rsync3.txt 2001-09-12 16:35:39.000000000 +0200 +++ rsync-2.6.6_patch/rsync3.txt 2006-01-19 18:20:33.957510912 +0100 @@ -124,10 +124,6 @@ - Scripting support. - - Propagate atimes and do not modify them. This is very ugly on - Unix. It might be better to try to add O_NOATIME to kernels, and - call that. - - Unicode. Probably just use UTF-8 for everything. - Open authentication system. Can we use PAM? Is SASL an adequate diff -uNr rsync-2.6.6/rsync.c rsync-2.6.6_patch/rsync.c --- rsync-2.6.6/rsync.c 2005-03-14 18:06:08.000000000 +0100 +++ rsync-2.6.6_patch...

Here's an assortment of build and run-time fixes for various architectures that we've applied in Debian. Ben. Aurelien Jarno (1): ppc64: fix struct stat Ben Hutchings (2): MIPS: Update archfcntl.h syscalls: Override detection of direct socket syscalls on i386, m68k, s390 Helge Deller (1): Add pread and pwrite 32bit syscall wrappers for parisc Mauricio Faria de Oliveira

On 06/23/2015 08:10 PM, Marko Vojinovic wrote: > Ok, you made me curious. Just how dramatic can it be? From where I'm > sitting, a read/write to a disk takes the amount of time it takes, the > hardware has a certain physical speed, regardless of the presence of > LVM. What am I missing? Well, there's best and worst case scenarios. Best case for file-backed VMs is

...root_path = realpath(argv[1], NULL); + if (!root_path) { + ret = errno; + usage(ret); + } + + subvol_path = realpath(argv[2], NULL); + if (!subvol_path) { + ret = errno; + usage(ret); + } + + r.full_subvol_path = subvol_path; + r.root_path = root_path; + + subvol_fd = open(subvol_path, O_RDONLY|O_NOATIME); + if (subvol_fd < 0) { + ret = errno; + fprintf(stderr, "ERROR: Subvolume open failed. %s\n", + strerror(ret)); + goto out; + } + + ret = pthread_attr_init(&t_attr); + if (ret < 0) { + fprintf(stderr, "ERROR: pthread init failed. %s\n", + strerror(ret)); + g...