[Ocfs2-devel] OCFS2 features RFC - separate journal?

[Daniel Phillips]

Mark Fasheh wrote:
> Out of curiousity, are we talking about a single journal device (all slot 
 > journals on one disk) or one device per journal?

Hi Mark,

For me, all journals on one disk, but that is just what I want for my one
particular project.  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.

I don't see that there is anything to be gained by requiring the user to
specify a different device for each journal since the user tools already
have to handle the case where all the journals are on the same device.

The configuration I am most interested at the moment has two nodes, each
of which exports one NVRAM disk and one normal disk to the other.  The
NVRAM disks form a mirror with two journals on it.  The normal disks
likewise form a mirror with the OCFS2 fs proper on it.  The latter
volume needs to be snapshotted and its mirror needs a dirty map.  The
dirty map will live on the (NVRAM) journal volume.  See how big a deal
it is to be able to factor out the journals like that?  As I mentioned
earlier, the journals don't need to be snapshotted and the mirror
doesn't need a dirty map, which is a really big help considering that
typical write latency is determined by the journal, and the latency of
a snapshoted, mirrored device with a persistent dirty map can get really
high.

A picture:

                Node0  <---- GigE cable  ---->  Node1
   NVRAM:   Slot0 Journal               Mirror of Slot0 Journal
            Slot1 Journal               Mirror of Slot1 Journal
            HDISK Dirty Map             Mirror of HDISK Dirty Map

   HDISK:   OCFS2 FS proper             Mirror of OCFS2 FS proper
            OCFS2 FS Snapshot Store     Mirror of OCFS2 FS Snapshot Store

As a side note, separate journals will allow the user to be much less
conservative about setting the number of slots.

Regards,

Daniel