From: Josef Bacik <josef@redhat.com>
To: Christian Brunner <christian@brunner-muc.de>
Cc: Sage Weil <sage@newdream.net>, Josef Bacik <josef@redhat.com>,
linux-btrfs@vger.kernel.org, ceph-devel@vger.kernel.org
Subject: Re: Ceph on btrfs 3.4rc
Date: Thu, 10 May 2012 13:40:38 -0400 [thread overview]
Message-ID: <20120510174038.GA2061@localhost.localdomain> (raw)
In-Reply-To: <CAJafhzSgaQ3sx=Af0Ru0CiwQH37V5y8jgjoTo_8yozcjo9rpPA@mail.gmail.com>
On Fri, Apr 27, 2012 at 01:02:08PM +0200, Christian Brunner wrote:
> Am 24. April 2012 18:26 schrieb Sage Weil <sage@newdream.net>:
> > On Tue, 24 Apr 2012, Josef Bacik wrote:
> >> On Fri, Apr 20, 2012 at 05:09:34PM +0200, Christian Brunner wrote:
> >> > After running ceph on XFS for some time, I decided to try btrfs again.
> >> > Performance with the current "for-linux-min" branch and big metadata
> >> > is much better. The only problem (?) I'm still seeing is a warning
> >> > that seems to occur from time to time:
> >
> > Actually, before you do that... we have a new tool,
> > test_filestore_workloadgen, that generates a ceph-osd-like workload on the
> > local file system. It's a subset of what a full OSD might do, but if
> > we're lucky it will be sufficient to reproduce this issue. Something like
> >
> > test_filestore_workloadgen --osd-data /foo --osd-journal /bar
> >
> > will hopefully do the trick.
> >
> > Christian, maybe you can see if that is able to trigger this warning?
> > You'll need to pull it from the current master branch; it wasn't in the
> > last release.
>
> Trying to reproduce with test_filestore_workloadgen didn't work for
> me. So here are some instructions on how to reproduce with a minimal
> ceph setup.
>
> You will need a single system with two disks and a bit of memory.
>
> - Compile and install ceph (detailed instructions:
> http://ceph.newdream.net/docs/master/ops/install/mkcephfs/)
>
> - For the test setup I've used two tmpfs files as journal devices. To
> create these, do the following:
>
> # mkdir -p /ceph/temp
> # mount -t tmpfs tmpfs /ceph/temp
> # dd if=/dev/zero of=/ceph/temp/journal0 count=500 bs=1024k
> # dd if=/dev/zero of=/ceph/temp/journal1 count=500 bs=1024k
>
> - Now you should create and mount btrfs. Here is what I did:
>
> # mkfs.btrfs -l 64k -n 64k /dev/sda
> # mkfs.btrfs -l 64k -n 64k /dev/sdb
> # mkdir /ceph/osd.000
> # mkdir /ceph/osd.001
> # mount -o noatime,space_cache,inode_cache,autodefrag /dev/sda /ceph/osd.000
> # mount -o noatime,space_cache,inode_cache,autodefrag /dev/sdb /ceph/osd.001
>
> - Create /etc/ceph/ceph.conf similar to the attached ceph.conf. You
> will probably have to change the btrfs devices and the hostname
> (os39).
>
> - Create the ceph filesystems:
>
> # mkdir /ceph/mon
> # mkcephfs -a -c /etc/ceph/ceph.conf
>
> - Start ceph (e.g. "service ceph start")
>
> - Now you should be able to use ceph - "ceph -s" will tell you about
> the state of the ceph cluster.
>
> - "rbd create -size 100 testimg" will create an rbd image on the ceph cluster.
>
> - Compile my test with "gcc -o rbdtest rbdtest.c -lrbd" and run it
> with "./rbdtest testimg".
>
> I can see the first btrfs_orphan_commit_root warning after an hour or
> so... I hope that I've described all necessary steps. If there is a
> problem just send me a note.
>
Well it's only taken me 2 weeks but I've finally git it all up and running,
hopefully I'll reproduce. Thanks,
Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-05-10 17:40 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
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 [this message]
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=20120510174038.GA2061@localhost.localdomain \
--to=josef@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=christian@brunner-muc.de \
--cc=linux-btrfs@vger.kernel.org \
--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