[Top] [All Lists]

Re: Extended attributes limit in Linux

To: Sun_Blood <sblood@xxxxxxxxx>
Subject: Re: Extended attributes limit in Linux
From: Chris Murphy <lists@xxxxxxxxxxxxxxxxx>
Date: Mon, 3 Feb 2014 13:51:41 -0700
Cc: xfs@xxxxxxxxxxx
Delivered-to: xfs@xxxxxxxxxxx
In-reply-to: <CAMN6oR=c3o5ayAdG010mh=9AZu0EbkU_zR4FptFA_egnbqt=8Q@xxxxxxxxxxxxxx>
References: <CAMN6oR=a0G6O-3CVVkTwhYKavJTa543U3MLezCM8KW1ASZcPnA@xxxxxxxxxxxxxx> <52EB64DC.4020603@xxxxxxxxxx> <1391165083.4275.7.camel@ubuntu> <52EB960D.607@xxxxxxxxxx> <1391172723.4275.11.camel@ubuntu> <52EBA783.1080801@xxxxxxxxxx> <1391178074.4275.19.camel@ubuntu> <52EBB431.50301@xxxxxxxxxx> <6C94A326-DADE-4A32-97F6-AE84E9F57777@xxxxxxxxx> <1D87A7C9-988F-4F61-A577-67300DAF2554@xxxxxxxxxxx> <14FE2575-4C84-43B8-9992-F91ABE2B6F26@xxxxxxxxx> <83F9F221-9387-47D5-B67C-E9252056E408@xxxxxxxxxxxxxxxxx> <CAMN6oR=c3o5ayAdG010mh=9AZu0EbkU_zR4FptFA_egnbqt=8Q@xxxxxxxxxxxxxx>

On Feb 3, 2014, at 12:14 AM, Sun_Blood <sblood@xxxxxxxxx> wrote:

On Mon, Feb 3, 2014 at 2:15 AM, Chris Murphy <lists@xxxxxxxxxxxxxxxxx> wrote:

On Feb 2, 2014, at 7:33 AM, Sun_Blood <sblood@xxxxxxxxx> wrote:
> I will make a bug report for rsync also that it should not try to copy files with EA bigger then the destination can handle. But it would be great if XFS could handle this files and be fully compatible with OS X backups.

What application(s) are creating such files on OS X? Or how are they coming to have such large extended attributes?

Chris Murphy

They are created by Adobe Photoshop and/or iPhoto.

I'm finding that Photoshop CS6 and older use resource fork to store thumbnail previews, but with API changes occurring since OS X 10.4. such requests for the resource fork actually end up as an extended attribute. This appears with xattr -l as com.apple.ResourceFork. In two example files they are about 50KB each.

Photoshop CC doesn't create thumbnails using resource forks anymore, thus this extended attribute isn't created. Plus the OS X Finder creates thumbnail previews directly from supported file types, even if a thumbnail preview resource isn't available. And last, the Resource Manager is deprecated as of OS X 10.8.x, so I'd expect even com.apple.ResourceFork to eventually go away (i.e. any application wanting to write a resource to the resource fork will fail).

The way I'd characterize data in com.apple.ResourceFork is that it's disposable data. That is, any application developer who cared about data, wouldn't store it in com.apple.ResourceFork. And this isn't a recent sentiment.

Are you seeing significant extended attribute data other than com.apple.ResourceFork in these files?

Chris Murphy
<Prev in Thread] Current Thread [Next in Thread>