similar to: Does file.info man page describe ctime corrrectly?

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

Why does inserting an empty quote ("") into a rsync command cause the current directory to be backed up? Not sure if this is a UNIX-syntax question or rsync-syntax question. Code: #!/bin/sh echo "\nspace between quotes has no effect; only music is backed up:" rsync -ilrtn " " /home/wolf/music /backups/backup1 echo "\nempty quotes backs up current directory

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

struct timespec64 has unused bits in the tv_nsec field that can be used for other purposes. In future patches, we're going to change how the inode->i_ctime is accessed in certain inodes in order to make use of them. In order to do that safely though, we'll need to eradicate raw accesses of the inode->i_ctime field from the kernel. Add new accessor functions for the ctime that we can

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

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

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 =

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

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

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

Greetings all- I am conducting security testing on a device that uses Linux 2.4 with ext3. I am testing secure overwrite of remnant data in temporary files, but have run into a real good stumpper in the way Ext allocates data blocks. I've got 10 yrs of *NIX behind me, several with Linux, and this has really got me perplexed as I can't find any documentation explaining the subject

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

I'm trying to clone a volume in a storage pool and I'm following the steps described here: http://libvirt.org/docs/libvirt-appdev-guide-python/en-US/html/libvirt_application_development_guide_using_python-Storage_Pools-Cloning.html My code looks like: destXML = """ <volume>

https://bugzilla.samba.org/show_bug.cgi?id=13735 Bug ID: 13735 Summary: Synchronize files when the sending side has newer change times while modification times and sizes are identical on both sides Product: rsync Version: 3.1.3 Hardware: All OS: All Status: NEW

Hi, Recently I noticed file.copy() would discard the file mode information. Is this the expected behaviour or a bug for file.copy()? > file.create('testfile') [1] TRUE > file.info('testfile') size isdir mode mtime ctime testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39 atime uid gid uname grname

Hi, Recently I noticed file.copy() would discard the file mode information. Is this the expected behaviour or a bug for file.copy()? > file.create('testfile') [1] TRUE > file.info('testfile') size isdir mode mtime ctime testfile 0 FALSE 644 2011-03-05 17:06:39 2011-03-05 17:06:39 atime uid gid uname grname

Hi there, i still have a weird problem with Powerpoint an Excel files stored on a Samba share. Only read on if you -use a samba share as MULTI-user file repository (no force_user etc.) -where multiple, different users share files in common directories -the modification time of a file is of any relevance to you. (seems like lots of folks don?t bother access rights or keep their information

I've been working on a patchset to change how the inode->i_ctime is accessed in order to give us conditional, high-res timestamps for the ctime and mtime. struct timespec64 has unused bits in it that we can use to implement this. In order to do that however, we need to wrap all accesses of inode->i_ctime to ensure that bits used as flags are appropriately handled. This patchset first