From owner-freebsd-questions@FreeBSD.ORG Tue Jul 2 22:00:30 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5B79FDB3 for ; Tue, 2 Jul 2013 22:00:30 +0000 (UTC) (envelope-from keramida@ceid.upatras.gr) Received: from tux-cave.hellug.gr (tux-cave.hellug.gr [195.134.99.74]) by mx1.freebsd.org (Postfix) with ESMTP id B757018F8 for ; Tue, 2 Jul 2013 22:00:29 +0000 (UTC) X-Spam-Status: No X-Hellug-MailScanner-From: keramida@ceid.upatras.gr X-Hellug-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-2.9, required 5, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90) X-Hellug-MailScanner: Found to be clean X-Hellug-MailScanner-ID: r62LxCvU016773 Received: from giorgos.local.local (217-162-217-29.dynamic.hispeed.ch [217.162.217.29]) (authenticated bits=0) by tux-cave.hellug.gr (8.14.4/8.14.4/Debian-4) with ESMTP id r62LxCvU016773 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Wed, 3 Jul 2013 00:59:20 +0300 From: keramida@ceid.upatras.gr (Giorgos Keramidas) To: Chris Maness Subject: Re: OT: rsync on Mac OSX References: <67um8rd2r07ipc.fsf@saturn.laptop> Date: Tue, 02 Jul 2013 23:59:06 +0200 In-Reply-To: (Chris Maness's message of "Tue, 2 Jul 2013 14:48:03 -0700") Message-ID: <67um8r61wsei8l.fsf@saturn.laptop> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (darwin) MIME-Version: 1.0 Content-Type: text/plain Cc: "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 02 Jul 2013 22:00:30 -0000 On Tue, 2 Jul 2013 14:48:03 -0700, Chris Maness wrote: >On Tue, Jul 2, 2013 at 2:30 PM, Giorgos Keramidas wrote: >>On Tue, 2 Jul 2013 13:35:00 -0700, Chris Maness 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.