public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Sun_Blood <sblood@gmail.com>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: Jeff Liu <jeff.liu@oracle.com>, xfs@oss.sgi.com
Subject: Re: Extended attributes limit in Linux
Date: Sun, 2 Feb 2014 15:33:27 +0100	[thread overview]
Message-ID: <14FE2575-4C84-43B8-9992-F91ABE2B6F26@gmail.com> (raw)
In-Reply-To: <1D87A7C9-988F-4F61-A577-67300DAF2554@dubeyko.com>


[-- Attachment #1.1: Type: text/plain, Size: 2586 bytes --]


On 1 feb 2014, at 15:08, Vyacheslav Dubeyko <slava@dubeyko.com> wrote:

> 
> On Jan 31, 2014, at 10:25 PM, Sun_Blood wrote:
> 
>> 
>> On 31 jan 2014, at 15:33, Jeff Liu <jeff.liu@oracle.com> wrote:
>> 
>>> 
>>> On 01/31 2014 22:21 PM, Vyacheslav Dubeyko wrote:
>>>> On Fri, 2014-01-31 at 21:39 +0800, Jeff Liu wrote:
>>>> 
>>>>>> 
>>>>>> I checked the same under Mac OS X 10.6.8 (Snow Leopard). And I have
>>>>>> failed on 3803 bytes size of xattr. So, I suppose that you have Mac OS X
>>>>>> Lion. And EAs is larger under Lion yet.
>>>>>> 
>>>>>> What version of Mac OS X have you?
>>>>>> 
>>>>> Yup, Mountain Lion v10.8.4 :)
>>>>> 
>>>> 
>>>> I suspect that xattrs with significant size is stored in compressed
>>>> state on HFS+. I implemented support of compressed xattrs partially but
>>>> I don't share this code yet. But, yes, EAs with size greater than 64 KB
>>>> can be a problem.
>> 
>> 
>> FYI, Example of output from one of the failing files. First from OS X and then same file after failed copy to XFS.
>> 
>> OS X Maverik:
>> file: "/Users/username/Pictures/iPhoto Library/Database/apdb/BigBlobs.apdb"
>> type: "\0\0\0\0"
>> creator: "\0\0\0\0"
>> attributes: avbstclinmedz
>> created: 01/25/2014 11:43:17
>> modified: 01/28/2014 20:02:46
>> 
>> 
>> Ubunutu 
>> getfattr: Removing leading '/' from absolute path names
>> # file: srv/nas/home/apple_bak_rsync/username/Pictures/iPhoto Library/Database/BigBlobs.apdb
>> user.com.apple.quarantine="0006;52e39545;iPhoto;”
> 
> 
> Sorry, but I don't quite follow your thought. What do you show by this output?
> What do you mean? Could you describe in more details?
> 
> Thanks,
> Vyacheslav Dubeyko.

Sorry late reply. The output is just to show what happen after I transfer a file from OS X to XFS that has EA bigger then 64k(I think). When I try for example to rsync this file from OS X to Linux XFS I get this error:
rsync: rsync_xal_set: lsetxattr(""/srv/nas/home/apple_bak_rsync/xxxxxx/Pictures/iPhoto Library/Database/BigBlobs.apdb"","user.com.apple.FinderInfo") failed: Operation not permitted (1)

But also rsync can give this error.
rsync: rsync_xal_set: lsetxattr(""/srv/danne/extern2/1000_EXT/2013/2013-03-05/IMG_6872-Edit.tif"","user.com.apple.ResourceFork") failed: Argument list too long (7)

Is this 2 errors related?

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.

//Martin

[-- Attachment #1.2: Type: text/html, Size: 3545 bytes --]

[-- Attachment #2: Type: text/plain, Size: 121 bytes --]

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2014-02-02 14:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-31  7:40 Extended attributes limit in Linux Sun_Blood
2014-01-31  8:54 ` Jeff Liu
2014-01-31 10:44   ` Vyacheslav Dubeyko
2014-01-31 12:24     ` Jeff Liu
2014-01-31 12:52       ` Vyacheslav Dubeyko
2014-01-31 13:39         ` Jeff Liu
2014-01-31 14:21           ` Vyacheslav Dubeyko
2014-01-31 14:33             ` Jeff Liu
2014-01-31 19:25               ` Sun_Blood
2014-02-01 14:08                 ` Vyacheslav Dubeyko
2014-02-02 14:33                   ` Sun_Blood [this message]
2014-02-02 15:12                     ` Jeff Liu
2014-02-02 15:22                       ` Jeff Liu
2014-02-02 15:31                         ` Sun_Blood
2014-02-03  1:15                     ` Chris Murphy
2014-02-03  7:14                       ` Sun_Blood
2014-02-03 20:51                         ` Chris Murphy
2014-02-02 21:37   ` Dave Chinner
2014-02-03  7:19     ` Sun_Blood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=14FE2575-4C84-43B8-9992-F91ABE2B6F26@gmail.com \
    --to=sblood@gmail.com \
    --cc=jeff.liu@oracle.com \
    --cc=slava@dubeyko.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox