From: Christoph Hellwig <hch@infradead.org>
To: David Zafman <david.zafman@inktank.com>
Cc: Loic Dachary <loic@dachary.org>,
"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
xfs@oss.sgi.com
Subject: Re: xattr limits
Date: Fri, 4 Oct 2013 04:16:40 -0700 [thread overview]
Message-ID: <20131004111640.GA22948@infradead.org> (raw)
In-Reply-To: <31BF914D-D406-428E-8671-0005901E10E6@inktank.com>
Might be good to send the crash report to the XFS list..
On Thu, Oct 03, 2013 at 11:54:29PM -0700, David Zafman wrote:
>
> Here is the test script:
>
>
> David Zafman
> Senior Developer
> http://www.inktank.com
>
>
>
>
> On Oct 3, 2013, at 11:02 PM, Loic Dachary <loic@dachary.org> wrote:
>
> > Hi David,
> >
> > Would you mind attaching the script to the mail for completness ? It's a useful thing to have :-)
> >
> > Cheers
> >
> > On 04/10/2013 01:21, David Zafman wrote:
> >>
> >> I want to record with the ceph-devel archive results from testing limits of xattrs for Linux filesystems used with Ceph.
> >>
> >> Script that creates xattrs with name user.test1, user.test2, ?. on a single file
> >> 3.10 linux kernel
> >>
> >> ext4
> >> value bytes number of entries
> >> 1 148
> >> 16 103
> >> 256 14
> >> 512 7
> >> 1024 3
> >> 4036 1
> >> Beyond this immediately get ENOSPC
> >>
> >> btrfs
> >> value bytes number of entries
> >> 8 10k
> >> 16 10k
> >> 32 10k
> >> 64 10k
> >> 128 10k
> >> 256 10k
> >> 512 10k slow but worked 1,000,000 got completely hung for minutes at a time during removal strace showed no forward progress
> >> 1024 10k
> >> 2048 10k
> >> 3096 10k
> >> Beyond this you start getting ENOSPC after fewer entries
> >>
> >> xfs (limit entries due to xfs crash with 10k entries)
> >> value bytes number of entries
> >> 1 1k
> >> 8 1k
> >> 16 1k
> >> 32 1k
> >> 64 1k
> >> 128 1k
> >> 256 1k
> >> 512 1k
> >> 1024 1k
> >> 2048 1k
> >> 4096 1k
> >> 8192 1k
> >> 16384 1k
> >> 32768 1k
> >> 65536 1k
> >>
> >> --
> >> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> >> the body of a message to majordomo@vger.kernel.org
> >> More majordomo info at http://vger.kernel.org/majordomo-info.html
> >>
> >
> > --
> > Lo?c Dachary, Artisan Logiciel Libre
> > All that is necessary for the triumph of evil is that good people do nothing.
> >
>
---end quoted text---
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
parent reply other threads:[~2013-10-04 11:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <31BF914D-D406-428E-8671-0005901E10E6@inktank.com>]
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=20131004111640.GA22948@infradead.org \
--to=hch@infradead.org \
--cc=ceph-devel@vger.kernel.org \
--cc=david.zafman@inktank.com \
--cc=loic@dachary.org \
--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