similar to: mtime, atime, ctime

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

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.org

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

Often we need to preserve the information atime conveys, but I have found no way to get rsync to preserve this, nor any hint it is being worked on. It would be great if 'rsync -t' also set atime not just mtime -- or maybe a new option is desired for atime. I don't know if the -X mentioned in "NEWS file from CVS" covers this: > Added the --xattrs (-X) option to preserver

It looks like I need to elaborate further to get a feedback. I checked the rsync source code and it is using utime() to restore atime file attribute. It is fine to change ctime for that transferred file in this case. What we are having problem is that when rsync gets kicked off and transfers one file to the destination, this action changes ctime of "all" files in the same

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,

Dear Martin Pool. We regularly use rsync for making backups of our file systems but we have noticed that the atimes are not transferred with the files and are also always updated on the sender's side. Therefore, we have created a modified version of rsync based on rsync-2.6.6 protocol version 29 which transfers the access times with the transferred files and also allows to preserve the access

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 \

Hi, I looked though documentation and also checked last 9 months of archives, but could not find the corresponding information. We are having an issue with incremental backup with arkeia. Arkeia checks if ctime/mtime of the file are changed, if so, it backs up. I realized that when I ran rsync from a cammnd line, it changed ctime, and preserved atime of the file in a destination as

I find rsync an excellent tool when I need to move multi-gigabyte filesystems, because I can do most of the copying during the week - then a quick cleanup sweep in our 4 hour outage window. I do need to somehow get the atime's to copy over, because as it stands now I loose the age information (which we will soon be using for auto-archiving) on things I copy with rsync. Would it be that hard

Version 2.1.10 For some reason Mutt doesn't list any info about IMAP folders and seems to ignore folder_format. My questions is does anyone have any workarounds for this?

I posted a patch a few days ago that adds copying of atime. At that time, it was just enabled with -t/--times. After some time, we have figured out that that choice might not have been the best. Here's a new version of the patch (relative to CVS) that adds -A/--copy-atime instead. It also includes a test case. Any feedback on this patch and/or the previous one that I posted?

schilytools star has the ability to restore ctimes from tarfiles. This is useful when restoring filesystems as root in single user mode, and I thought I'd like rsync to do the same. I started working off the rsync-patches/atimes.diff patch but noticed that this patch is buggy and presently does not work. (It fails to set the atime and it fails to set the mtime too). Even if this is fixed

On 8 September 2015 at 13:57, Kevin Korb <kmk at sanitarium.net> wrote: Hi Kevin. > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > The ctime will always be newer or the same as the mtime. This is > because changing the mtime also changes the ctime as does other things > like changing the permissions. > > Rsync only pays attention to the mtime because rsync can

Hi, We use an rsync (rrsync, to be precise) based back-up solution. Every so often an iSCSI based file-system gets brought up and left connected for the night. After a mount event rsync will back that volume up, including server TB of data that haven't been modified, but the ctime is newer than the mtime. Is there a way to stop this behaviour? Cheers, Andrej

On Wed, 11 Jan 2006, joe wrote: >> Environment: > RELENG_4 20051028 >> Description: > [cp fails to update atime] > > this occurs regardless of whether or not the user has > rwx permissions on the source file. does not apply of > course if the source filesystem is mounted read-only. > they are read-write here. > > since the source file is indeed being read,

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> >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I would need to see both your existing rsync command line and the output of --itemize-changes when such an occurrence happens before I can really understand what is happening. In the end, if you have any output at all the bare minimum should be - --itemize-changes. --verbose is utterly useless without it. On 09/07/2015 11:10 PM, Andrej wrote: >

Hi Everyone, The following feature request was received by a Debian user; could you comment on it? I think this seems reasonable, but perhaps should be enabled only conditionally (as if the argument parser isn't stressed enough). Thanks, Justin On Fri, Jul 23, 2004 at 05:09:09PM -0300, Pedro Zorzenon Neto wrote: > Package: rsync > Version: 2.6.2-2 > Severity: wishlist > Tags:

We should call ocfs2_inode_lock_atime instead of ocfs2_inode_lock in ocfs2_file_splice_read like we do in ocfs2_file_aio_read so that we can update atime in splice read if necessary. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/file.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/ocfs2/file.c b/fs/ocfs2/file.c index 775ac34..95cba48 100644