From: "Alexey Polyakov" <alexey.polyakov@gmail.com>
To: "Łukasz Mierzwa" <prymitive@pcserwis.net>
Cc: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: reiser4 resize
Date: Wed, 20 Sep 2006 13:00:20 +0400 [thread overview]
Message-ID: <b5d90b2a0609200200s5838456bm618093395356390a@mail.gmail.com> (raw)
In-Reply-To: <op.tf52pansd4os1z@localhost>
On 9/20/06, £ukasz Mierzwa <prymitive@pcserwis.net> wrote:
> It's been proven that flushes are doing much more job then they should.
> Not so long ago someone send a trace of block device io accesess during
> reiser4 work and someone anylized it and said that some files or parts of
> file where written over and over 200 times or so. Bittottent downloads on
> a few months old filesystem that had been used often just shows a week
> spot in reiser4, while downloading files with azureus with only 64KB of
> data per second I got disk lid on almost all the time, swithcing to
> rtorrent helped as it does not seem to call fsync ( I think I disabled
> fsync in azureus).
Ah, I see, if bittorrent calls fsync often, it's no wonder that
reiser4 behaves badly. I had to preload libnosync for some of my
programs that do fsync to avoid this.
--
Alexey Polyakov
next prev parent reply other threads:[~2006-09-20 9:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-19 1:12 reiser4 resize Jack Byer
2006-09-19 13:23 ` Vladimir V. Saveliev
2006-09-19 17:54 ` David Masover
2006-09-20 7:39 ` Alexey Polyakov
[not found] ` <op.tf52pansd4os1z@localhost>
2006-09-20 9:00 ` Alexey Polyakov [this message]
2006-09-21 7:30 ` David Masover
2006-09-21 7:49 ` Łukasz Mierzwa
2006-09-21 7:52 ` Łukasz Mierzwa
2006-09-21 7:48 ` David Masover
2006-09-20 1:09 ` Jack Byer
-- strict thread matches above, loose matches on Subject: below --
2008-01-25 14:38 Reiser4 resize Oleg Osovitskiy
2008-01-30 20:40 ` Edward Shishkin
2008-03-02 22:39 No space left on rfs4 Christopher Sawtell
2008-03-03 20:59 ` Reiser4 resize John
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=b5d90b2a0609200200s5838456bm618093395356390a@mail.gmail.com \
--to=alexey.polyakov@gmail.com \
--cc=prymitive@pcserwis.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).