From: Daniel Phillips <phillips@google.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] OCFS2 features RFC - separate journal?
Date: Fri, 05 May 2006 20:09:24 -0700 [thread overview]
Message-ID: <445C1364.2020208@google.com> (raw)
In-Reply-To: <20060505182500.GC21588@ca-server1.us.oracle.com>
Mark Fasheh wrote:
> Hi Daniel,
> On Thu, May 04, 2006 at 08:05:16PM -0700, Daniel Phillips wrote:
>>The user should be able to specify slot by slot which
>>device the journal is on, if it is not on the main volume. This is just
>>the logical extension of the Ext3 scheme.
>
> To be honest, that sounds a little bit like overkill to me.
>
> For example, I was imagining that the user could create a seperate, rootless
> file system on the journal device - similar to how we do heartbeat only file
> systems. The normal file system would have the journal file system UUID
> stored in it's superblock. This way mount.ocfs2 could find the proper disk
> on the system and pass it along to the file system. If we had multiple
> possible journal devices, it would at least mean a much larget set of UUID's
> to store, necessitating a seperate area on disk for them. I'm sure there are
> other implications as well.
Hi Mark,
Why do you want to wrap the separate journals in a filesystem instead of just
being devices?
> Thanks for explaining your proposed setup. What are you using to mirror the
> devices?
DDRaid over NBD or iSCSI, probably NBD (which leads the performance race at
the moment).
Regards,
Daniel
next prev parent reply other threads:[~2006-05-06 3:09 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 18:35 [Ocfs2-devel] OCFS2 features RFC Mark Fasheh
2006-04-25 21:55 ` Christoph Hellwig
2006-04-25 22:24 ` Mark Fasheh
2006-04-26 16:50 ` Daniel Phillips
2006-04-26 4:11 ` Andi Kleen
2006-04-26 18:06 ` Mark Fasheh
2006-04-26 18:08 ` Andi Kleen
2006-04-26 18:34 ` Daniel Phillips
2006-04-27 20:25 ` Paul Taysom
2006-05-03 23:04 ` [Ocfs2-devel] OCFS2 features RFC - separate journal? Daniel Phillips
2006-05-04 0:29 ` Zach Brown
2006-05-04 0:46 ` Daniel Phillips
2006-05-04 20:56 ` Zach Brown
2006-05-04 20:59 ` Wim Coekaerts
2006-05-04 22:23 ` Daniel Phillips
2006-05-04 22:30 ` Mark Fasheh
2006-05-05 3:05 ` Daniel Phillips
2006-05-05 18:25 ` Mark Fasheh
2006-05-06 3:09 ` Daniel Phillips [this message]
2006-05-05 17:12 ` Paul Taysom
2006-05-05 18:06 ` Daniel Phillips
2006-05-05 18:57 ` Sunil Mushran
2006-05-08 14:28 ` Paul Taysom
2006-05-08 17:43 ` Daniel Phillips
2006-05-08 18:00 ` Paul Taysom
2006-05-08 18:22 ` Daniel Phillips
2006-05-11 20:04 ` [Ocfs2-devel] OCFS2 features RFC Jeff Mahoney
2006-05-11 20:40 ` Paul Taysom
2006-05-11 20:55 ` Joel Becker
2006-05-11 21:16 ` Daniel Phillips
2006-05-17 1:44 ` Mark Fasheh
[not found] ` <446BBCF5.7040903@google.com>
[not found] ` <20060518024638.GY21588@ca-server1.us.oracle.com>
2006-05-19 0:35 ` Daniel Phillips
2006-05-19 15:16 ` J. Bruce Fields
2006-05-20 6:11 ` Mark Fasheh
2006-05-22 19:18 ` Daniel Phillips
2006-05-22 17:01 ` Paul Taysom
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=445C1364.2020208@google.com \
--to=phillips@google.com \
--cc=ocfs2-devel@oss.oracle.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 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.