From: Dave Chinner <david@fromorbit.com>
To: Emmanuel Florac <eflorac@intellique.com>
Cc: xfs@oss.sgi.com
Subject: Re: XFS filesystem setfacl has limitation?
Date: Thu, 8 Mar 2012 13:40:53 +1100 [thread overview]
Message-ID: <20120308024053.GN3592@dastard> (raw)
In-Reply-To: <20120307221613.1014ea82@galadriel.home>
On Wed, Mar 07, 2012 at 10:16:13PM +0100, Emmanuel Florac wrote:
> Le Wed, 7 Mar 2012 15:42:42 +1100 vous écriviez:
>
> > It's basically a limitation of the on-disk format definition that
> > has been carried over from Irix. It is an arbitrary limit - the real
> > limit is the maximum size of an attribute (64KB) and we plan to
> > raise it to that limit as part of the upcoming on-disk format
> > changes for metadata checksums...
> >
>
> What's the proposed time frame or kernel version for this change?
When it is ready. Think months, not years ;)
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-03-08 2:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F56C4D5.1070206@eisoo.com>
2012-03-07 4:42 ` XFS filesystem setfacl has limitation? Dave Chinner
2012-03-07 21:16 ` Emmanuel Florac
2012-03-08 2:40 ` Dave Chinner [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=20120308024053.GN3592@dastard \
--to=david@fromorbit.com \
--cc=eflorac@intellique.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