Date: Tue, 02 Jul 2013 23:59:06 +0200 From: keramida@ceid.upatras.gr (Giorgos Keramidas) To: Chris Maness <chris@chrismaness.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: OT: rsync on Mac OSX Message-ID: <67um8r61wsei8l.fsf@saturn.laptop> In-Reply-To: <CANnsUMF8udkQq=qQaUEGPtW9-LXsbrmdx0va_8cd_AhfnGB%2B8A@mail.gmail.com> (Chris Maness's message of "Tue, 2 Jul 2013 14:48:03 -0700") References: <CANnsUMGyULjmK%2BQYeJHggZ6B2082wCPvU-8E_qcyg4j2OMrSWg@mail.gmail.com> <67um8rd2r07ipc.fsf@saturn.laptop> <CANnsUMF8udkQq=qQaUEGPtW9-LXsbrmdx0va_8cd_AhfnGB%2B8A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 2 Jul 2013 14:48:03 -0700, Chris Maness <chris@chrismaness.com> wrote:
>On Tue, Jul 2, 2013 at 2:30 PM, Giorgos Keramidas <keramida@ceid.upatras.gr>wrote:
>>On Tue, 2 Jul 2013 13:35:00 -0700, Chris Maness <chris@chrismaness.com> wrote:
>>> I have been using rsync with Mac OSX with no issues until today. I
>>> generally use it instead of the copy command because if the copy fails
>>> on large files, I can pick up where I left off. I have backed up
>>> entire Final Cut Pro projects this way with no issues. However, I
>>> recently synced a drive to a folder in another drive, and the OS does
>>> not recognize the final rendered files as quicktime files. The files
>>> work fine in the parent drive. I have no idea what might be going on.
>>> I used the flags: rsync -vaur like I always do. Any suggestions?
>>
>> This is a FreeBSD list, so any issues rsync may have with MacOS X are
>> not very relevant to what FreeBSD is doing or would do. Having said
>> that though, can you try without the -u option? Maybe modification
>> times are newer on the target drive and rsync skips everything.
>>
>> You should probably also enable --stats and have a look at the final
>> report of rsync, to see if it actually sync'ed any files, or skipped all
>> of them because of mtime checks.
>
> Yep, the files copied, and I used "touch" to force them to recopy.
> However, the files that were copied are not recognizable by their native
> aps. Just big junk files. I have no clue what happened. I am just
> copying everything by a simple cut and paste this time. However, this
> directory is HUGE and I won't know until about 18 hours from now.
Since you are going to wait anyway, why don't you try peeking at some of
the file checksums while this is running?
MacOS X comes with a shasum utility which implements SHA-256 checksums,
so you should be able to look at a few random samples of these files,
e.g. by running on the source disk:
shasum -a 256 source_directory/file/path/to/some/file.ext
shasum -a 256 copied_directory/file/path/to/some/file.ext
If these are the same, then the applications look elsewhere, e.g. in the
'hidden' .DS_Store stuff some MacOS directories contain.
But if the checksums are different, well, then there's your problem.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67um8r61wsei8l.fsf>