From: Christoph Hellwig <hch@infradead.org>
To: Sage Weil <sage@newdream.net>
Cc: Christian Brunner <chb@muc.de>,
ceph-devel@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: ceph on btrfs [was Re: ceph on non-btrfs file systems]
Date: Tue, 25 Oct 2011 06:23:30 -0400 [thread overview]
Message-ID: <20111025102330.GA18415@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1110240941500.15349@cobra.newdream.net>
On Mon, Oct 24, 2011 at 10:06:49AM -0700, Sage Weil wrote:
> > - When I run ceph with btrfs snaps disabled, the situation is getting
> > slightly better. I can run an OSD for about 3 days without problems,
> > but then again the load increases. This time, I can see that the
> > ceph-osd (blkdev_issue_flush) and btrfs-endio-wri are doing more work
> > than usual.
>
> FYI in this scenario you're exposed to the same journal replay issues that
> ext4 and XFS are. The btrfs workload that ceph is generating will also
> not be all that special, though, so this problem shouldn't be unique to
> ceph.
What journal replay issues would ext4 and XFS be exposed to?
next prev parent reply other threads:[~2011-10-25 10:23 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 1:54 ceph on non-btrfs file systems Sage Weil
2011-10-24 16:22 ` Christian Brunner
2011-10-24 17:06 ` ceph on btrfs [was Re: ceph on non-btrfs file systems] Sage Weil
2011-10-24 19:51 ` Josef Bacik
2011-10-24 20:35 ` Chris Mason
2011-10-24 21:34 ` Christian Brunner
2011-10-24 21:34 ` Christian Brunner
2011-10-24 21:37 ` Arne Jansen
2011-10-25 11:56 ` Christian Brunner
2011-10-25 12:23 ` Josef Bacik
2011-10-25 12:23 ` Josef Bacik
2011-10-25 14:25 ` Christian Brunner
2011-10-25 15:00 ` Josef Bacik
2011-10-25 15:00 ` Josef Bacik
2011-10-25 15:05 ` Josef Bacik
2011-10-25 15:05 ` Josef Bacik
2011-10-25 15:13 ` Christian Brunner
2011-10-25 15:13 ` Christian Brunner
2011-10-25 20:15 ` Chris Mason
2011-10-25 20:22 ` Josef Bacik
2011-10-26 0:16 ` Christian Brunner
2011-10-26 0:16 ` Christian Brunner
2011-10-26 8:21 ` Christian Brunner
2011-10-26 8:21 ` Christian Brunner
2011-10-26 13:23 ` Chris Mason
2011-10-27 15:07 ` Josef Bacik
2011-10-27 18:14 ` Josef Bacik
2011-10-25 16:36 ` Sage Weil
2011-10-25 19:09 ` Christian Brunner
2011-10-25 19:09 ` Christian Brunner
2011-10-25 22:27 ` Sage Weil
2011-10-27 19:52 ` Josef Bacik
2011-10-27 19:52 ` Josef Bacik
2011-10-27 20:39 ` Christian Brunner
2011-10-27 20:39 ` Christian Brunner
[not found] ` <CAO47_-_+Oqs1sHeYEBfxgwugSUYKftQLQ9jEyDgFPFu8fXe34w@mail.gmail.com>
[not found] ` <CAO47_-8YGAxoYOBRKxLP2HULqEtV5bMugzzybq3srCVFZczgGA@mail.gmail.com>
2011-10-31 10:25 ` Christian Brunner
2011-10-31 13:29 ` Christian Brunner
2011-10-31 14:04 ` Josef Bacik
2011-10-25 10:23 ` Christoph Hellwig [this message]
2011-10-25 16:23 ` Sage Weil
[not found] <CAO47_-9L7SdQwhJ27B6yzrqG8xvj+CeZHeSutgeCixcv7kUidg@mail.gmail.com>
[not found] ` <Pine.LNX.4.64.1110252221510.6574@cobra.newdream.net>
2011-10-26 8:12 ` Christian Brunner
2011-10-26 8:12 ` Christian Brunner
2011-10-26 16:32 ` Sage Weil
[not found] <4EA86FD7.4030407@tuxadero.com>
2011-10-27 10:53 ` Martin Mailand
2011-10-27 10:59 ` Stefan Majer
2011-10-27 10:59 ` Stefan Majer
2011-10-27 11:17 ` Martin Mailand
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=20111025102330.GA18415@infradead.org \
--to=hch@infradead.org \
--cc=ceph-devel@vger.kernel.org \
--cc=chb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.