All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward@namesys.com>
To: JP Howard <jh_lists@fastmail.fm>,
	Andreas Dilger <adilger@clusterfs.com>,
	ReiserFS List <reiserfs-list@namesys.com>,
	green@namesys.com
Subject: Re: External journals and NVRAM devices
Date: Sat, 02 Nov 2002 00:58:40 +0300	[thread overview]
Message-ID: <3DC2F910.DF56232D@namesys.com> (raw)
In-Reply-To: 3DC2F8E4.AD84886F@namesys.com

Edward Shishkin wrote:
> 
> JP Howard wrote:
> >
> > On Fri, 01 Nov 2002 17:30:18 +0300, "Edward Shishkin"
> > <edward@namesys.com> said:
> > > Yes. And the experience said that external logging brings a bit better
> > > effect for this journal mode then for other ones.
> > >
> > > > >Is there a command to show the current journal size?
> > >
> > > #debugreiserfs main_device
> > >
> > Hmmm...
> > ----
> > Blocksize: 4096
> > <...>
> > Journal parameters:
> > <...>
> >         Size 8193 blocks (including 1 for journal header) (first block
> >         18)
> > ----
> >
> > So my journal is only 32k?
> 
> Yes. Standard journal can be only 32K.

Sorry, 32M!

> 
>  With Ext3 I used 192MB journal in data=journal
> > mode. Should I be using a size around that when using data=journal with
> > ReiserFS too? Why is the default so low?--is it because the data logging
> > patches don't automatically change it?
> 
> Reiserfs journal size doesn't depend on journal mode.
> 
> > >
> > > The journal size remains the same unless you specify another one by
> > > reiserfstune utility.
> > >
> > And non-standard journal sizes don't work under 2.4, right? Or are there
> > patches for this that are reasonably stable?
> 
> Yes they are. Let me specify it on next week unless Oleg will do it earlier.
> Edward.

  reply	other threads:[~2002-11-01 21:58 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-01 20:38 External journals and NVRAM devices JP Howard
2002-11-01 20:57 ` Valdis.Kletnieks
2002-11-01 21:57 ` Edward Shishkin
2002-11-01 21:58   ` 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  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  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=3DC2F910.DF56232D@namesys.com \
    --to=edward@namesys.com \
    --cc=adilger@clusterfs.com \
    --cc=green@namesys.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.