similar to: question for file attributes (atime, ctime)

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

Lets say you had 4 servers and you wanted to setup replicate and distribute. What methoid would be better: server sdb1 xen0 brick0 xen1 mirror0 xen2 brick1 xen3 mirror1 replicate block0 - brick0 mirror0 replicate block1 - brick1 mirror1 distribute unify - block0 block1 or server sdb1 sdb2 xen0 brick0 mirror3 xen1 brick1 mirror0 xen2 brick2 mirror1 xen3 brick3 mirror2 replicate block0 -

Hi, I can't manage to get rsync's --link-dest option working. Here is a step by step script which doesn't produce the good results. # create test dir mkdir testrsync cd testrsync mkdir orig echo "abcd" > orig/testfile # create a mirror rsync -apog orig/ mirror/ # create another mirror using link-dest rsync -apog --link-dest=mirror/ orig/ mirror2/ # look at inodes ls

Hey guys, i tried to create a simple rsync script that should create daily backups from a ZFS storage and put them into a timestamp folder. After creating the initial full backup, the following backups should only contain "new data" and the rest will be referenced via hardlinks (-link-dest) This was at least a simple enough scenario to achieve it with my pathetic scripting skills.

Hello guys, I have two mirrors. I need to compare files and directories on both mirrors and as a result print list of those which are missing on mirror 2 What i did find /data > find.mirror1 find /data > find.mirror2 Now i need to get list of those directories which are missing in mirror1. Thanks in advance! David -------------- next part -------------- An HTML attachment was

The package elfutils-debuginfod-client is needed for even a minimal install, but it is not available on most mirrors. I suspect some are excluding mirroring debuginfo packages with just a *debuginfo* pattern to rsync, where they should do something like *-debuginfo-*.rpm (which should be good for now as I don't see any package with just "debuginfo" in the name, even in Fedora). The

The scripts I use analyze the rsync log after it completes and then sftp's a summary to the root of the just completed rsync. If no summary is found or the summary is that it failed, the folder rotation for that set is skipped and that folder is re-used on the subsequent rsync. The key here is that the folder rotation script runs separately from the rsync script(s). For each entity I want

Hi, Arthur found out that ext3 is not changing the ctime on the "old_dir" (the object that is being renamed), but ext2 does. It looks to me like this is simply an omission of the following little patch from namei.c - Peter - --- fs/ext3/namei.c.orig Mon Mar 19 22:55:03 2001 +++ fs/ext3/namei.c Mon Mar 19 22:53:40 2001 @@ -985,6 +985,13 @@ new_dir->i_version =

-----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 set a specific mtime (--times) but setting a specific ctime is impossible as it would violate the basic *nix security model.

-----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, file.info is producing data.frame with ctime variable. Help file says that on Unix this is 'last status change' and on Windows 'creation time'. Is there a way to get 'last status change' on Windows using some R function? Thanks, Johannes

(R 2.8.0 on Debian GNU/Linux sid) ?file.info contains: mtime, ctime, atime: integer of class '"POSIXct"': file modification, creation and last access times. This implies that ctime is "file [...] creation [...] time" Has R implemented ctime differently to Unix? I understand, on Linux at least, that ctime is the last change time (not the creation time).

Problem: Want to be able to produce a qcow2 file with multiple ext4 File Systems. Days later want to reproduce the production of the qcow2 and have the exact same byte-for-byte file, to prove my build is reproducible. Currently the ctime attributes of the inodes will differ and thus the qcow2 files will differ. Since the file times are subsecond the trick of setting the system time and chmoding

In ctime updating of xattr, it use the wrong type of access for inode, so use ocfs2_journal_access_di instead. Signed-off-by: Tao Ma <tao.ma at oracle.com> --- fs/ocfs2/xattr.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/fs/ocfs2/xattr.c b/fs/ocfs2/xattr.c index 915039f..e393315 100644 --- a/fs/ocfs2/xattr.c +++ b/fs/ocfs2/xattr.c @@ -2592,8 +2592,9 @@

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

Synopsis: cp(1) does not update atime of the source file State-Changed-From-To: open->closed State-Changed-By: dds State-Changed-When: Fri Dec 14 08:33:46 UTC 2007 State-Changed-Why: This problem has been fixed in RELENG_6. Pending MFC is no longer pertinent. http://www.freebsd.org/cgi/query-pr.cgi?pr=91622

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,

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