From: Vladimir Saveliev <vs@namesys.com>
To: Ash <ashrat@gmail.com>
Cc: reiserfs-list@namesys.com
Subject: Re: MAX_TRANS_AGE tuning
Date: Wed, 06 Oct 2004 14:37:33 +0400 [thread overview]
Message-ID: <1097059052.13026.19.camel@tribesman.namesys.com> (raw)
In-Reply-To: <e96ff1200410040532787d4c62@mail.gmail.com>
Hello
On Mon, 2004-10-04 at 16:32, Ash wrote:
> Sorry, accidently sent the previous message before completing the compose. :-(
>
> What is the difference between JOURNAL_MAX_TRANS_AGE and JOURNAL_MAX_COMMIT_AGE
> defined in reiserfs_fs.h ?
>
> I see that both are set to 30 as default. Would reducing the either of
> them to lower
> values give more persistency in filesystem operations in post-crash scenarios ?
>
Reducing JOURNAL_MAX_TRANS_AGE should cause transactions to flush
earlier. Once a transaction is flushed - it will be replaied on
post-crash reboot.
> What are the side-effects of changing these values ?
>
> Thanks,
> Ash
>
>
> On Mon, 4 Oct 2004 17:59:48 +0530, Ash <ashrat@gmail.com> wrote:
> > Hi
> >
> > What is the difference between
> >
>
prev parent reply other threads:[~2004-10-06 10:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-04 12:29 MAX_TRANS_AGE tuning Ash
2004-10-04 12:32 ` Ash
2004-10-06 10:37 ` Vladimir Saveliev [this message]
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=1097059052.13026.19.camel@tribesman.namesys.com \
--to=vs@namesys.com \
--cc=ashrat@gmail.com \
--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.