All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Liu <jeff.liu@oracle.com>
To: Sun_Blood <sblood@gmail.com>, Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: xfs@oss.sgi.com
Subject: Re: Extended attributes limit in Linux
Date: Sun, 02 Feb 2014 23:22:21 +0800	[thread overview]
Message-ID: <52EE62AD.4030509@oracle.com> (raw)
In-Reply-To: <52EE6069.7090905@oracle.com>


On 02/02 2014 23:12 PM, Jeff Liu wrote:
> 
> On 02/02 2014 22:33 PM, Sun_Blood wrote:
<snip>
>>>> 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?
> 
> Those errors are unrelated IMO, the first one is due to the permission rules but
> I'm not sure the root cause, the second one is occurred as the EA value is larger
> than 64K I guess.
>  
>>
>> 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.
> 
> 64K size is not limited by XFS directly, it is limited by VFS setxattr syscall.
> IOWs, EA set operation is not yet get into XFS when "Argument list too long" error
> is returned, so I think you would ran into the same error on other file systems
> which are support 64K EA value size as well.

To be more precise, larger EA set operation would not works via setxattr(2) on Linux
regardless of the underlying file systems :).

Thanks,
-Jeff

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

  reply	other threads:[~2014-02-02 15:22 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
2014-02-02 15:12                     ` Jeff Liu
2014-02-02 15:22                       ` Jeff Liu [this message]
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=52EE62AD.4030509@oracle.com \
    --to=jeff.liu@oracle.com \
    --cc=sblood@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.