From: Dave Chinner <david@fromorbit.com>
To: Timothy Shimmin <tes@sgi.com>
Cc: "Linda A. Walsh" <xfs@tlinx.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: Question about extended attributes...
Date: Fri, 1 Aug 2008 22:32:53 +1000 [thread overview]
Message-ID: <20080801123253.GG6201@disturbed> (raw)
In-Reply-To: <4892B361.9030900@sgi.com>
On Fri, Aug 01, 2008 at 04:55:29PM +1000, Timothy Shimmin wrote:
> Hi Linda,
>
> Linda A. Walsh wrote:
> > my man page says extended xfs attributes can have 256-byte names
> > with up to 64K of data.
> >
> > Is there a limit on the number of extended attributes max data size or
> > name size?
> >
> > I.e. could I have 1000 attributes with 64K of data each?
> >
> Yep.
>
> > Is there a strong reason why the file and data sizes were limited to
> > 256/64K?
....
> I'm not sure why 64K was chosen for a value size limit.
Because changes to EAs are journalled. Hence there must be a bound
size limit because log space is limited.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2008-08-01 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-01 0:11 Question about extended attributes Linda A. Walsh
2008-08-01 6:55 ` Timothy Shimmin
2008-08-01 12:32 ` Dave Chinner [this message]
2008-08-04 5:13 ` Timothy Shimmin
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=20080801123253.GG6201@disturbed \
--to=david@fromorbit.com \
--cc=tes@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