From owner-freebsd-questions@FreeBSD.ORG Fri Jul 12 18:10:54 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 3402E2C9 for ; Fri, 12 Jul 2013 18:10:54 +0000 (UTC) (envelope-from bc979@lafn.org) Received: from zoom.lafn.org (zoom.lafn.org [108.92.93.123]) by mx1.freebsd.org (Postfix) with ESMTP id E5A7D15D7 for ; Fri, 12 Jul 2013 18:10:53 +0000 (UTC) Received: from [10.0.1.3] (static-71-177-216-148.lsanca.fios.verizon.net [71.177.216.148]) (authenticated bits=0) by zoom.lafn.org (8.14.3/8.14.2) with ESMTP id r6CI9ak6063933 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Fri, 12 Jul 2013 11:09:39 -0700 (PDT) (envelope-from bc979@lafn.org) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: OT: rsync on Mac OSX From: Doug Hardie In-Reply-To: Date: Fri, 12 Jul 2013 11:09:37 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <6EC7DF61-0243-4BB3-904B-7289F574B256@lafn.org> References: <67um8rd2r07ipc.fsf@saturn.laptop> <67um8r61wsei8l.fsf@saturn.laptop> To: Chris Maness X-Mailer: Apple Mail (2.1508) X-Virus-Scanned: clamav-milter 0.97 at zoom.lafn.org X-Virus-Status: Clean Cc: Giorgos Keramidas , "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: Fri, 12 Jul 2013 18:10:54 -0000 On 12 July 2013, at 10:49, Chris Maness wrote: > On Tue, Jul 2, 2013 at 3:11 PM, Chris Maness = wrote: >=20 >>=20 >>=20 >>=20 >>=20 >>> Since you are going to wait anyway, why don't you try peeking at = some of >>> the file checksums while this is running? >>>=20 >>> 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: >>>=20 >>> shasum -a 256 source_directory/file/path/to/some/file.ext >>>=20 >>> shasum -a 256 copied_directory/file/path/to/some/file.ext >>>=20 >>> If these are the same, then the applications look elsewhere, e.g. in = the >>> 'hidden' .DS_Store stuff some MacOS directories contain. >>>=20 >>> But if the checksums are different, well, then there's your problem. >>>=20 >>>=20 >>=20 > Checksums are the same. All other files still work however the HUGE > rendered Final Cut Pro output, so I guess it is something in = .DS_Store. > Last time I just gave up and recopied everything by a simple cut and = paste > and that solved the problem. I made a small change on the project = today, > and I don't want to have to copy the WHOLE thing again just for a = small > delta. I already synced the directories, but the new rendered files = are > still un-openable in any application even though the checksums match. > Really weird. However, the project will still open and work on FCP. = Just > the 12Gb rendered movie files will not play on anything even FCP. If = I > delete .DS_Store will the system regenerate it with the appropriate = file > associations? >=20 > I know this is a little off topic, but Mac OSX is based on BSD. You = guys > are also the smartest around :D Rsync on the Mac only opens and copies the data forks. It does not copy = the resource forks. There are still a few applications that use = resource forks. Likewise the checksum apps work on the data forks only. There is a utility that is a modified rsync that does handle resource = forks. I no longer remember what its name is. Its been a number of = years since I last used it. I normally rsync from FreeBSD systems to = Mac systems. I use Minis as off-site backups.