public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ryan Cumming <ryan@spitfire.gotdns.org>
To: linux-kernel@vger.kernel.org
Subject: Re: [RFC] ext3 documentation (lack of)
Date: Tue, 17 Aug 2004 23:01:06 -0700	[thread overview]
Message-ID: <200408172301.09350.ryan@spitfire.gotdns.org> (raw)
In-Reply-To: <20040818025951.63c4134e.diegocg@teleline.es>

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

On Tuesday 17 August 2004 17:59, you wrote:
> +commit=nrsec	(*)	Ext3 can be told to write all its data and metadata
> +			every 'nrsec' seconds. The default value is 5 seconds.
> +			This means that if you lose your power, you will lose,
> +			as much, the latest 5 seconds of work. This default
> +			value (or any low value) will hurt performance, but
> +			it's good for data-safety. Setting it to 0 disables it.
> +			Disabling it or setting it to very large values will
> +			improve performance,

Setting commit to zero doesn't seem to disable it, judging from my local 
2.6.8.1-mm1 source.

super.c has:
case Opt_commit:
   if (match_int(&args[0], &option))
      return 0;
   if (option < 0)
      return 0;
   if (option == 0)
      option = JBD_DEFAULT_MAX_COMMIT_AGE;
   sbi->s_commit_interval = HZ * option;
   break;

Where JBD_DEFAULT_COMMIT_AGE is defined to 5 in include/linux/jbd.h. So it 
seems that setting it to zero will just set it to the default commit interval 
of 5 seconds. Am I missing something?

-Ryan

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-08-18  6:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18  0:59 [RFC] ext3 documentation (lack of) Diego Calleja
2004-08-18  6:01 ` Ryan Cumming [this message]
2004-08-18 11:38   ` Diego Calleja
2004-08-18 12:24     ` Janusz Dziemidowicz
2004-08-18 12:59       ` Helge Hafting
2004-08-18 17:17         ` Andreas Dilger
2004-08-18 16:42       ` Diego Calleja
2004-08-19  9:57         ` Janusz Dziemidowicz

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=200408172301.09350.ryan@spitfire.gotdns.org \
    --to=ryan@spitfire.gotdns.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox