From: Chris Mason <mason@suse.com>
To: Henrique Faria <henrique@streamworks.com.br>
Cc: Reiserfs mail-list <Reiserfs-List@Namesys.COM>
Subject: Re: Data loss during power off
Date: 27 Jun 2002 15:08:50 -0400 [thread overview]
Message-ID: <1025204930.1853.3.camel@tiny> (raw)
In-Reply-To: <20020627183410.20055.qmail@hm47.locaweb.com.br>
On Thu, 2002-06-27 at 11:34, Henrique Faria wrote:
> Well, changing both JOURNAL_MAX_TRANS_AGE and JOURNAL_MAX_COMMIT_AGE to 0.1
> and making the following configuration for flash devices
>
> JOURNAL_BLOCK_COUNT 512
> JOURNAL_TRANS_MAX 128
> JOURNAL_MAX_BATCH 127
>
> I was able to force data flush just after the file write C instructions
> (with O_SYNC or fsync). I did not get performance problems for while, maybe
> because it's a linux dedicated for a single game.
>
All of the journal parameters should be ints. Setting them to 0.1 won't
have quite the desired effect.
If you have JOURNAL_MAX_BATCH set to 1, you can ignore JOURNAL.*AGE, and
the transaction will commit after each write.
-chris
next prev parent reply other threads:[~2002-06-27 19:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-26 15:34 Data loss during power off Henrique Faria
2002-06-27 8:01 ` Nikita Danilov
2002-06-27 8:53 ` Philippe Gramoullé
2002-06-27 8:58 ` Nikita Danilov
2002-06-27 14:52 ` Henrique Faria
2002-06-27 17:58 ` Nikita Danilov
2002-06-27 15:34 ` Henrique Faria
2002-06-27 19:08 ` Chris Mason [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-25 21:09 Henrique Faria
2002-06-26 0:31 ` Michael Chang
2002-06-26 5:08 ` Oleg Drokin
2002-06-27 14:53 ` Chris Mason
2002-06-27 12:36 ` Henrique Faria
2002-06-27 16:48 ` Chris Mason
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=1025204930.1853.3.camel@tiny \
--to=mason@suse.com \
--cc=Reiserfs-List@Namesys.COM \
--cc=henrique@streamworks.com.br \
/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.