> Date: Wed, 20 Jan 2016 23:04:20 -0800
> From: Wayne Davison
> On Thu, Dec 25, 2014 at 2:48 AM, Ingo Br=C3=BCckl
wrote:
> > On systems using nanoseconds differences should be taken into
> > consideration.
> The problem is that if you transfer from a filesystem that ha
[Included text copied from the commit.]
> Date: Sun, 24 Jan 2016 19:52:49 +
> From: samba-b...@samba.org
> Auto-Submitted: auto-generated
> https://bugzilla.samba.org/show_bug.cgi?id=11521
> Wayne Davison changed:
>What|Removed |
> Date: Sun, 24 Jan 2016 15:43:20 -0800
> From: Wayne Davison
A couple questions below; please bear with me.
> No, if you do a ext4 -> ext4 copy, rsync has set the matching ns info for
> transferred files since 3.1.0. There was a case prior to rsync 3.1.2 where
> a brand-new
If you're thinking about changing the way attrs work, here's a
question for you. I just recently started trying to use them for the
first time, in backing up a Windows host via a wrapper script that
runs the remote rsync under Cygwin on the Windows side, by mounting
the source disk as a VSS snapsh
> Date: Fri, 08 Mar 2013 22:26:24 -0500
> From: Kevin Korb
> If it were me, based on my previous experience, I would shut down both
> systems and run memtest86+ or "Windows Memory Diagnostics" on both
> systems. Make sure to enable the extended tests. Let them run
> over
