similar to: RFE: ctime byte-for-byte reproducible qcow2 ext2/3/4 FS

As the minimum block size to discard in qcow2 is 64K, any point in fstrimming smaller contiguous blocks? TIA, Y.

I work for a school dist, and I am having a bit of trouble with the "Student Server" We have about 3000 students all with their own accounts. I had the samba server setup to share their home directories but their home directories are the same as their login name. So jamie.mcparland would be an example of a share name. But in Win 9X it gets truncated to jamie.mcparla then we get the error

I'm trying to use rsync to keep the permissions between two Windows servers. A windows NT 4 server (with rsync daemon) and windows 2003 R2 I use Rsync in a batch file and I run it as Administrator by double clicking on it. Typically: set cygwin=notnsec rsync -rpDPo --chmod=Du+rwx,Fu+rwx,+X and the files are crossed over but the permissions are screwed up. Now, I can't find out the

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

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

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

Hi, I have gone through the patches that are used in the Fedora package and probably only the "mkcert-permissions" [1] can be considered to be included upstream. It is dated into package version 1.0-0.beta2.3, but I cannot find any particular reason for the inclusion (like a bug in bugzilla, etc.). Some (winbind support, quota warnings) were obsoleted by dovecot 1.1, two are used for

Thought I would write some notes about how I got an APC BackUPS XS 1500 working with newhidups under Gentoo 2006.0. The specific issue here is the permissions on the device files used that libusb uses to access the USB hardware. I followed Peter Selinger's instructions at http://www.mscs.dal.ca/~selinger/ups/backups.html on getting newhidups going with an APC device. The sticking point for

If I have an image of a filesystem taken with dd, I can look at it with a hex editor and discover that an ext2/3 superblock is at offset 1024 and I can figure out a lot of info about it. I cannot figure out, however, how the superblock differs from ext2 in ext3. I can't tell them apart... the "magic number" is the same as well as the "revision" field. If I have such an

Hey there I recently downloaded a folder off an ftp that had [hxc] as the bwginning name of thr dir, now it says it's locked when I try to delete it in KDE. when I try to rm -f in a console it says it doesn't exist, I can't move it, delete it , or change anything about it. When I output a ls -la to a txt it says this about it "drwxr-xr-x 2 root root 4096 Dec 2

Hi, i''m striving to capistranize a foo app on DH. Everything is hosted on DH to simplify a bit : - svn repository (http access) - the application - the DB I used the recipe of Jamis Buck modified by Geoffrey Grosenbach which you can find here : http://nubyonrails.com/pages/shovel_dreamhost I did the least modifications possible. As recommended. 1) When I launch the

I'm running 2.11, and I've noticed a number of log entries that look like so: angie.log: tdb(/usr/local/samba/var/locks/locking.tdb): expand_file ftruncate to 8192 failed (Permission denied) [2004/10/03 15:14:36, 0] tdb/tdbutil.c:tdb_log(531) tdb(/usr/local/samba/var/locks/brlock.tdb): expand_file ftruncate to 8192 failed (Permission denied) The files in question look like this:

I'm running 2.11, and I've noticed a number of log entries that look like so: angie.log: tdb(/usr/local/samba/var/locks/locking.tdb): expand_file ftruncate to 8192 failed (Permission denied) [2004/10/03 15:14:36, 0] tdb/tdbutil.c:tdb_log(531) tdb(/usr/local/samba/var/locks/brlock.tdb): expand_file ftruncate to 8192 failed (Permission denied) The files in question look like this:

I am going to convert my 32-bit Debian system to a 64-bit Debian system today. But, after I move my maildir files over to the new hard drive the ctimes are going to get modified to current time and mess up my automatic purge scripts for the Deleted Items folders. Is it possible for me to either keep the existing ctimes or is it possible for me to modify the ctimes to the date headers of the

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

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

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