From: Austin S Hemmelgarn <ahferroin7@gmail.com>
To: Richard Sharpe <realrichardsharpe@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Can BTRFS handle XATTRs larger than 4K?
Date: Mon, 22 Dec 2014 13:09:16 -0500 [thread overview]
Message-ID: <54985E4C.40003@gmail.com> (raw)
In-Reply-To: <CACyXjPwiRXaV9ASetZa_cYD2R9TxQLfQP0x7aLknWuRXdtZ2Og@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1740 bytes --]
On 2014-12-22 12:27, Richard Sharpe wrote:
> On Mon, Dec 22, 2014 at 6:28 AM, Austin S Hemmelgarn
> <ahferroin7@gmail.com> wrote:
>> On 2014-12-19 21:07, Richard Sharpe wrote:
>>>
>>> Hi folks,
>>>
>>> I need a Linux file system that supports XATTRs up to 64K.
>>>
>>> Can BTRFS support that or is XFS the only Linux file system with such
>>> support?
>>>
>> At the moment, BTRFS is limited to xattrs that fit inline in the metadata
>> nodes (so ~3900 bytes for a 4k leafsize).
>>
>> XFS, however, isn't the only Linux filesystem that supports xattrs that
>> size. Assuming that you are using a recent kernel, you can also use such
>> xattrs on at least:
>> * XFS
>> * JFS
>> * ext4
>> * reiserfs (I think, not 100% certain about this one though)
>> * OCFS2 (even though it is technically a cluster fs, it can be run single
>> node without the clustering)
>> * ZFS (IIRC, ZFS supports unlimited xattr size)
>> * NTFS (no limit on xattr size, though you should use NTFS-3G instead of
>> the in-kernel driver)
>> * SquashFS (read-only)
>> * HFS+ (Also no limit on xattr size)
>> Of these, I'd personally suggest using XFS unless you need to be able to
>> shrink the filesystem, in which case I'd suggest ext4.
>
> Thanks for the info. I hadn't realized that ext4 had lifted the restriction.
>
Yeah, it would be nice if there was more clarity in the documentation.
Personally, I'd love to see unlimited length xattr's like NTFS and HFS+
do, as that would greatly improve interoperability (both Windows and OS
X use xattrs, although they call them 'alternative data streams' and
'forks' respectively), and provide a higher likelihood that xattrs would
start getting used more.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 2455 bytes --]
next prev parent reply other threads:[~2014-12-22 18:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-20 2:07 Can BTRFS handle XATTRs larger than 4K? Richard Sharpe
2014-12-20 8:38 ` Chris Murphy
2014-12-22 11:38 ` Chris Samuel
2014-12-22 11:41 ` Chris Samuel
2014-12-22 14:28 ` Austin S Hemmelgarn
2014-12-22 17:27 ` Richard Sharpe
2014-12-22 18:09 ` Austin S Hemmelgarn [this message]
2014-12-22 18:43 ` Chris Murphy
2014-12-22 19:56 ` Austin S Hemmelgarn
2014-12-22 20:06 ` Richard Sharpe
2014-12-22 20:44 ` Austin S Hemmelgarn
2014-12-22 20:50 ` Richard Sharpe
2014-12-22 22:52 ` Robert White
2014-12-22 22:55 ` Richard Sharpe
2014-12-23 0:08 ` Robert White
2014-12-23 1:16 ` Richard Sharpe
2014-12-23 12:37 ` Austin S Hemmelgarn
2014-12-22 23:15 ` ronnie sahlberg
2014-12-22 23:55 ` Robert White
2014-12-22 23:58 ` Richard Sharpe
2014-12-23 0:11 ` Robert White
2014-12-22 20:04 ` Richard Sharpe
2014-12-22 20:33 ` Austin S Hemmelgarn
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=54985E4C.40003@gmail.com \
--to=ahferroin7@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=realrichardsharpe@gmail.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;
as well as URLs for NNTP newsgroup(s).