All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Howard <jh_lists@fastmail.fm>
To: ReiserFS List <reiserfs-list@namesys.com>
Subject: External journals and NVRAM devices
Date: Fri, 01 Nov 2002 16:38:32 +1100	[thread overview]
Message-ID: <3DC21358.5040808@fastmail.fm> (raw)

Hi all,

I'm looking at buying solid state drives / NVRAM drives for our servers
to hold an external ReiserFS journal.

We are using 2.4.20pre11, and Chris Mason's data logging patches.

I'm looking for any tips on how large the journal is when using
data=journal, and whether the external log patches are stable and work OK
in data=journal mode. Is there a command to show the current journal
size? Does the size vary over time? We need to ensure we buy a card with
enough memory so this is important information for us.

Is anyone currently using NVRAM for the journal? If so, how do you find
the performance of this configuration?

TIA,
   Jeremy



             reply	other threads:[~2002-11-01  5:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01  5:38 Jeremy Howard [this message]
2002-11-01  6:29 ` External journals and NVRAM devices Andreas Dilger
2002-11-01 14:30   ` Edward Shishkin
2002-11-01 20:40 ` Hans Reiser
2002-11-01 21:45   ` Edward Shishkin
2002-11-01 20:41 ` Hans Reiser
2002-11-02  3:04   ` Andrew Clausen
  -- strict thread matches above, loose matches on Subject: below --
2002-11-01  7:29 JP Howard
2002-11-01  7:49 ` Serge Kolodeznyh
2002-11-01 15:33   ` Len Sorensen
2002-11-01 15:10 ` Edward Shishkin
2002-11-01 20:38 JP Howard
2002-11-01 20:57 ` Valdis.Kletnieks
2002-11-01 21:57 ` Edward Shishkin
2002-11-01 21:58   ` Edward Shishkin
2002-11-01 21:37 JP Howard
2002-11-04 13:16 ` Chris Mason
2002-11-05 21:23 ` reiser
2002-11-06 20:18   ` Andreas Dilger
2002-11-06 20:42     ` Chris Mason
2002-11-05 22:12 JP Howard

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=3DC21358.5040808@fastmail.fm \
    --to=jh_lists@fastmail.fm \
    --cc=reiserfs-list@namesys.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.