From: "João Eduardo Luís" <jecluis@gmail.com>
To: Christian Brunner <christian@brunner-muc.de>
Cc: Sage Weil <sage@newdream.net>, Josef Bacik <josef@redhat.com>,
ceph-devel@vger.kernel.org
Subject: Re: Ceph on btrfs 3.4rc
Date: Wed, 25 Apr 2012 13:16:19 +0100 [thread overview]
Message-ID: <4F97EB13.1050700@gmail.com> (raw)
In-Reply-To: <CAJafhzQ0BtNsUSr4cPYLg1MfMoKQhvYE3eS6VskRBeyJOF58iw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
On 04/25/2012 12:28 PM, Christian Brunner wrote:
> I've tried test_filestore_workloadgen, but it didn't work very well.
> After 5 Minutes it terminated with the following messages:
>
> 2012-04-25 11:28:57.768709 7fcac3f69760 0 Destroying collection
> '0.1_head' (358 objects)
> 2012-04-25 11:29:07.478747 7fcac3f69760 0 Destroying collection
> '0.22_head' (477 objects)
> 2012-04-25 11:29:07.479035 7fcac3f69760 0 We ran out of collections!
> 2012-04-25 11:29:07.916149 7fcac3f69760 1 journal close
> /dev/mapper/vg01-lv_osd_journal_0
>
> I guess this is not btrfs related .-)
>
Oh yeah... the "solution" for that is to set '--test-num-colls' to a
greater value (the test creates 30 by default, and destroys them every
'X' transactions). Increase the number of collections and it will have a
longer run.
But since that's sounding like a workaround over something that could
easily be avoided, I'll make a patch for the test to avoid that from
happening.
--
João Eduardo Luís
gpg key: 477C26E5 from pool.keyserver.eu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 554 bytes --]
next prev parent reply other threads:[~2012-04-25 12:16 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 15:09 Ceph on btrfs 3.4rc Christian Brunner
2012-04-23 7:20 ` Christian Brunner
2012-04-24 15:21 ` Josef Bacik
2012-04-24 16:26 ` Sage Weil
2012-04-24 17:33 ` Josef Bacik
2012-04-24 17:41 ` Neil Horman
2012-04-25 11:28 ` Christian Brunner
2012-04-25 12:16 ` João Eduardo Luís [this message]
2012-04-27 11:02 ` Christian Brunner
2012-05-03 14:13 ` Josef Bacik
2012-05-03 15:17 ` Josh Durgin
2012-05-03 15:20 ` Josef Bacik
2012-05-03 16:38 ` Josh Durgin
2012-05-03 19:49 ` Josef Bacik
2012-05-04 20:24 ` Christian Brunner
2012-05-09 20:25 ` Josef Bacik
2012-05-10 17:40 ` Josef Bacik
2012-05-10 20:35 ` Josef Bacik
2012-05-11 13:31 ` Josef Bacik
2012-05-11 18:33 ` Martin Mailand
2012-05-11 19:16 ` Josef Bacik
2012-05-14 14:19 ` Martin Mailand
2012-05-14 14:20 ` Josef Bacik
2012-05-16 19:20 ` Josef Bacik
2012-05-17 10:29 ` Martin Mailand
2012-05-17 14:43 ` Josef Bacik
2012-05-17 15:12 ` Martin Mailand
2012-05-17 19:43 ` Josef Bacik
2012-05-17 20:54 ` Christian Brunner
2012-05-17 21:18 ` Martin Mailand
2012-05-18 14:48 ` Josef Bacik
2012-05-18 17:24 ` Martin Mailand
2012-05-18 19:01 ` Josef Bacik
2012-05-18 20:11 ` Martin Mailand
2012-05-21 3:59 ` Miao Xie
2012-05-22 10:29 ` Christian Brunner
2012-05-22 17:33 ` Josef Bacik
2012-05-23 12:34 ` Christian Brunner
2012-05-23 14:12 ` Josef Bacik
2012-05-23 15:02 ` Josef Bacik
2012-05-23 19:12 ` Martin Mailand
2012-05-24 6:03 ` Martin Mailand
2012-05-24 9:37 ` Christian Brunner
2012-05-22 13:31 ` Josef Bacik
2012-05-11 13:46 ` Christian Brunner
2012-04-29 21:09 ` tsuna
2012-04-30 10:28 ` Christian Brunner
2012-04-30 10:54 ` Amon Ott
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=4F97EB13.1050700@gmail.com \
--to=jecluis@gmail.com \
--cc=ceph-devel@vger.kernel.org \
--cc=christian@brunner-muc.de \
--cc=josef@redhat.com \
--cc=sage@newdream.net \
/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