From: Emmanuel Florac <eflorac@intellique.com>
To: Laurent CARON <lcaron@lncsa.com>
Cc: xfs@oss.sgi.com
Subject: Re: Number of ACLs
Date: Thu, 7 Jul 2011 15:20:59 +0200 [thread overview]
Message-ID: <20110707152059.2e09f346@harpe.intellique.com> (raw)
In-Reply-To: <4E15AA1A.3090802@lncsa.com>
Le Thu, 07 Jul 2011 14:44:10 +0200
Laurent CARON <lcaron@lncsa.com> écrivait:
> I'd like to know if it is possible in a simple & safe way to increase
> the number of supported ACLs on an already existing FS.
>
> xfs_acl.h:
> #define XFS_ACL_MAX_ENTRIES 25
>
> Changing XFS_ACL_MAX_ENTRIES to something higher should do the trick,
> but will it be safe: ie: will I risk corrupting the FS this way ?
>
> I understand it'll imply a performance penalty if I add too many ACLs.
I asked recently to the list if there was any evolution on this point,
but unfortunately my question went ignored :(
Actually you can't simply change this entry and hope that it will
work; from what I understood, at best your filesystem will become
incompatible with any other kernel in the best case and you may need
to recompile the xfs tools too; in the worst case, compilation will
simply fail.
If you really need a lot of ACLs, the best answer so far is to use JFS,
which supports 1024 ACLs per file without tinkering and without pain.
The main culprit with JFS lies in relatively poor ageing (compared to
XFS), and no available tool to contain fragmentation. Imperfect world.
--
------------------------------------------------------------------------
Emmanuel Florac | Direction technique
| Intellique
| <eflorac@intellique.com>
| +33 1 78 94 84 02
------------------------------------------------------------------------
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-07-07 13:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 12:44 Number of ACLs Laurent CARON
2011-07-07 13:20 ` Emmanuel Florac [this message]
2011-07-07 13:26 ` Emmanuel Florac
2011-07-07 16:20 ` Laurent CARON
2011-07-08 3:42 ` Dave Chinner
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=20110707152059.2e09f346@harpe.intellique.com \
--to=eflorac@intellique.com \
--cc=lcaron@lncsa.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