All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Masover <ninja@slaphack.com>
To: "Łukasz Mierzwa" <prymitive@pcserwis.net>
Cc: "reiserfs-list@namesys.com" <reiserfs-list@namesys.com>
Subject: Re: The Infamous Reiser4-randomly-blocks-for-ages-and-writes-the-hd-continously-in-the-mean-while now with a btrace log! (hope it helps)
Date: Thu, 10 Aug 2006 16:59:30 -0400	[thread overview]
Message-ID: <44DB9E32.9010308@slaphack.com> (raw)
In-Reply-To: <op.td2z6u11d4os1z@localhost>

£ukasz Mierzwa wrote:
> Dnia Thu, 10 Aug 2006 20:48:59 +0200, David Masover <ninja@slaphack.com> 
> napisa³:
> 
>> Vesa Kaihlavirta wrote:
>>
>>> Incidentally, I've witnessed similar behaviour in various simple tasks,
>>> e.g. writing
>>> entries to an sqlite database, or receiving mail from pop3 in 
>>> thunderbird.
>>
>> Sounds like fsync issues.  That is being worked on.
> 
> I'm think it's writeout that's involved, I tried to disable fsync and it 
> helped for apps that are calling fsync to keep data integrity (like 
> sqlite) but it also happens when I'm downloading files using rtorrent 
> which does not call fsync but generetes many little writes.

Hmm.  Fragmentation, maybe?  Is this easily reproduceable with a 
freshly-formatted fs?

I'm just guessing here...

  reply	other threads:[~2006-08-10 20:59 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060806162017.GB8613@rvalles.homedns.org.>
2006-08-07  9:33 ` The Infamous Reiser4-randomly-blocks-for-ages-and-writes-the-hd-continously-in-the-mean-while now with a btrace log! (hope it helps) Nate Diller
2006-08-10 16:36   ` Vesa Kaihlavirta
2006-08-10 18:48     ` David Masover
2006-08-10 18:55       ` Łukasz Mierzwa
2006-08-10 20:59         ` David Masover [this message]
2006-08-10 21:06           ` Łukasz Mierzwa
2006-08-06 16:20 rvalles

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=44DB9E32.9010308@slaphack.com \
    --to=ninja@slaphack.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 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.