From: Ash <ashrat@gmail.com>
To: reiserfs-list@namesys.com
Subject: Re: MAX_TRANS_AGE tuning
Date: Mon, 4 Oct 2004 18:02:47 +0530 [thread overview]
Message-ID: <e96ff1200410040532787d4c62@mail.gmail.com> (raw)
In-Reply-To: <e96ff12004100405291b9f174c@mail.gmail.com>
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 ?
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
>
next prev parent reply other threads:[~2004-10-04 12:32 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 [this message]
2004-10-06 10:37 ` Vladimir Saveliev
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=e96ff1200410040532787d4c62@mail.gmail.com \
--to=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.