All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward@namesys.com>
To: JP Howard <jh_lists@fastmail.fm>
Cc: Andreas Dilger <adilger@clusterfs.com>,
	ReiserFS List <reiserfs-list@namesys.com>
Subject: Re: External journals and NVRAM devices
Date: Fri, 01 Nov 2002 18:10:31 +0300	[thread overview]
Message-ID: <3DC29967.ED587103@namesys.com> (raw)
In-Reply-To: 20021101072944.33C2B47683B@server5.fastmail.fm

JP Howard wrote:
> 
> On Thu, 31 Oct 2002 23:29:57 -0700, "Andreas Dilger"
> <adilger@clusterfs.com> said:
> > When people were testing this with ext3 external journals, they just
> > used a RAMDISK for getting the performance measurements.  Obviously,
> > (I hope ;-) this is not something you can do in real life, but for
> > performance measurement it is OK.
> >
> > Most people found that the ramdisk (and presumably the NVRAM device too)
> > didn't perform much, if any, better than having a separate fast disk for
> > the journal, because you are doing sequential I/O to the journal anyways.
> <...>
> 
> Yes, I'd heard something like this. Our servers aren't going to have a
> spare drive bay, I think, so a PCI NVRAM card may turn out to be a more
> economical solution (although I haven't received quotes back from the
> vendors yet...).
> 
> If I do find a spare drive bay, how unsafe would it be to use a single
> drive, rather than RAID 1 mirroring? What does ReiserFS do if it gets an
> IO error on the journal device? 

Reiserfs will want you to do following:
#reiserfsck --no-journal-available main_device
or 
#reiserfsck --no-journal-available --rebuild-tree main_device
then specify new journal device by reiserfstune.

>Could that bring down our whole system? I
> assume that it would--in which case using NVRAM would actually save two
> drive bays, since it should be reliable enough to not need redundency.
> 
> So, how big is a ReiserFS journal when using data=journal anyways?...

8192 blocks for reiserfs with standard journal.
The size of external journal device for non-standard.

Edward.

  parent reply	other threads:[~2002-11-01 15:10 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01  7:29 External journals and NVRAM devices JP Howard
2002-11-01  7:49 ` Serge Kolodeznyh
2002-11-01 15:33   ` Len Sorensen
2002-11-01 15:10 ` Edward Shishkin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-05 22:12 JP Howard
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-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  5:38 Jeremy Howard
2002-11-01  6:29 ` 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

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=3DC29967.ED587103@namesys.com \
    --to=edward@namesys.com \
    --cc=adilger@clusterfs.com \
    --cc=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.