From owner-freebsd-questions@FreeBSD.ORG Fri Jul 12 18:25:52 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 806DF28E for ; Fri, 12 Jul 2013 18:25:52 +0000 (UTC) (envelope-from christopher.maness@gmail.com) Received: from mail-vc0-x22c.google.com (mail-vc0-x22c.google.com [IPv6:2607:f8b0:400c:c03::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 3FEEB1756 for ; Fri, 12 Jul 2013 18:25:52 +0000 (UTC) Received: by mail-vc0-f172.google.com with SMTP id ib11so8009493vcb.3 for ; Fri, 12 Jul 2013 11:25:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=hbFEFti935GT0yfxEEmqnR40B2kPwSsYQQeKal1CXmA=; b=MXWrz6Bi7bPqgaJXP12P1ArIAmm3NyXq4j7b6Ff9wWus5VPUgBKk2zbIVlyd30F5q7 NAOKFZS2L227vdbQpB7p16Otu+/5Q43CfKmuEAckyhPcNI3dLcGSChyEuF9fWoLWQn5D aj/kZ9ODyocUWl34LJ9m3LAy18V7g6/8BnX8ExIqGV28/YC2ackSK9lCVqhRfv7iFU0U a3LGDdXzMa9d/VslaSSbxOmMseAGBIyrMHAqDv1Jg/ouh1N1deU+tmrbTQE1aV/Ni53p hSTkdsjycbjNEqQCAh8GkA4v6S/e2sZDeHFf5EZOwIwipKT6vEKwtvbf7khjLS9yraya Y7wA== MIME-Version: 1.0 X-Received: by 10.58.118.70 with SMTP id kk6mr25155787veb.1.1373653551664; Fri, 12 Jul 2013 11:25:51 -0700 (PDT) Sender: christopher.maness@gmail.com Received: by 10.58.220.105 with HTTP; Fri, 12 Jul 2013 11:25:51 -0700 (PDT) In-Reply-To: References: <67um8rd2r07ipc.fsf@saturn.laptop> <67um8r61wsei8l.fsf@saturn.laptop> Date: Fri, 12 Jul 2013 11:25:51 -0700 X-Google-Sender-Auth: viodNPFnS9D4w8B5oFPhCy-kbjE Message-ID: Subject: Re: OT: rsync on Mac OSX From: Chris Maness To: Paul Kraus , "freebsd-questions@freebsd.org" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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:25:52 -0000 On Fri, Jul 12, 2013 at 11:12 AM, Paul Kraus wrote: > Dropping the list =85 > > On Jul 12, 2013, at 1:49 PM, Chris Maness wrote: > > > 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 toda= y, > > 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 ar= e > > 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 fil= e > > associations? > > The .DS_Store files are created by the Finder when you view a directory. > Are both source and destination on Mac HFS+ volumes ? If so, then you are > probably missing the resource forks. > > Back in the very old days of Mac OS (way before 10.x), Mac OS files had > two parts, the data part that contained the, well, data, and the resource > fork that contained the meta-data that Mac OS used to associate a file wi= th > an application. HFS+ volumes on Mac OS X still include the resource forks= , > but "foreign" filesystems (NFS, UFS, FAT, etc.) do not. The work around > that Apple came up with is to create .DS_Store and ._ files to store > this metadata on non HFS+ volumes. > > You could try using ditto instead of rsync. ditto is a BSD derived copy > utility similar to rysnc, but I know that the Mac OS X version understand= s > resource forks and copies them as necessary. ditto may not be able to jus= t > copy changed blocks within a file, so you may still have to recopy the > entire file. > > But=85. I am also a little puzzled because applications on Mac OS X do no= t > NEED the resource fork to open a file, just to know which application to > use (and what options to hand it) to open a given file. A complete video > file, even without resource forks, should be able to be opened if you > explicitly telly he application to File -> Open =85. With the checksums > matching it is even odder. I expect that the large sizes (over 4 GB) are = a > contributing factor. > > Good luck and let me know what you find. > > -- > Paul Kraus > Deputy Technical Director, LoneStarCon 3 > Sound Coordinator, Schenectady Light Opera Company > > Thank you for the detailed description of what resource forks are. One more clue in this mystery is that appending .mov extension to it fixes the problem. I have never ran into this before, and I have even used rsync to back up movie projects before. It is not a big deal, but I always try to take the time to understand why things behave the way they do. I also suspect it has something to do with file size since all of the smaller files do not have this issue. Thanks, Chris Maness