From: Ben Myers <bpm@sgi.com>
To: Linda Walsh <xfs@tlinx.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: RFE: the manpage claims no limits on size of file extended attributes; has this now true?
Date: Tue, 23 Jul 2013 16:40:02 -0500 [thread overview]
Message-ID: <20130723214002.GM3111@sgi.com> (raw)
In-Reply-To: <51EEF543.5020305@tlinx.org>
Hey Linda,
On Tue, Jul 23, 2013 at 02:27:31PM -0700, Linda Walsh wrote:
> Ok, lemme rephrase my questions...
>
> The man page lists maximums for values at 64K, and names at 255
> characters. This implies these are the only limits one need worry about
> -- i.e. there is no limit on the maximum number of 255 byte names nor is
> there a limit on the sum of the values of attributes.
To the best of my knowledge:
There is no limit on the maximum number of extended attribute names.
There is no limit on the sum of the values of attributes.
The limit is on the sum of the names and values of all of the attributes in a
given inode.
> Is it something like 2^60 bytes?
Yeah, it's something big like that.
> or some such limit that no one will ever hit? Could
> I store alternate soundtracks for movies in attribute fields, or
> alternate scenes for movies?
Yep, you could do that. It's just that it would have to be done in 64k chunks.
Some time ago there was some discussion of supporting multiple file streams
which would not have the unfortunate 64k limitation, but nothing has come of
it so far.
Regards,
Ben
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-07-23 21:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 21:27 RFE: the manpage claims no limits on size of file extended attributes; has this now true? Linda Walsh
2013-07-23 21:40 ` Ben Myers [this message]
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=20130723214002.GM3111@sgi.com \
--to=bpm@sgi.com \
--cc=xfs@oss.sgi.com \
--cc=xfs@tlinx.org \
/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