All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vesa Kaihlavirta <vegai@iki.fi>
To: 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 19:36:16 +0300	[thread overview]
Message-ID: <44DB6080.8070306@iki.fi> (raw)
In-Reply-To: <5c49b0ed0608070233p68204fd1la2630e49fb08fad7@mail.gmail.com>

Nate Diller wrote:
> On 8/6/06, rvalles <rvalles@es.gnu.org> wrote:
>> The bug is as I've explained a thousand times. (and it does only affect
>> kernels newer than 2.6.12, all of them, that's one thing I'm sure)
>>
>> Newer kernels have a nice feature called "blktrace" to trace the block
>> layer activity. I include with this mail a log of the whole block (this
>> time it was just about 30 seconds, the previous one, when I was sending
>> a mail to a maillist, it was 10 minutes or maybe more).
>>
>> How did I do it:
>> - Write a mail to myself (small mail, btw).
>> - Start the btrace.
>> - Send it. (I pressed 'y' at mutt mail sending screen)
>> - Look at the HD led.
>> - When it stopped, the crap @ btrace stopped too. I then stopped btrace.
>>
>> I hope that this log helps enlighten someone.
>>
>> Now, to add to the data about the bug:
>> - My new desktop uses reiser4. It is affected, too.
>> - Just by typing "reboot" at my old desktop, the bug triggers inmediatly
>>   after the wall message is sent, and lasts about 10 minutes.
>> - Latest reiser4 fsck was run with --build-fs on my old desktop the day
>>   before; The FS had got, before that, some corrupcion (probably a bug)
>>   that caused kernel panics, so the FS is quite clean now, yet I can
>>   reproduce the bugs.
>>
>> I will be happy to help further in any way.
>>
>> I also have many friends who use reiser4 and are experiencing it; it
>> would be a shame if reiser4 finally got merged into the kernel with
>> this bug still there.
>
> 91% of the requests are 4K in size, 77% of requests are write
> barriers.  looks like there's something that causes bitmap blocks to
> be written synchronously.
>
> there's also a LOT of duplication, blocks that are written and then
> immediately RE-written.  the 4k block at sector 23246207 is written
> 226 times over the course of this trace, each time seemingly in a pair
> (write it, rewrite it, do other stuff, write it, re-write it, etc).
> this is pathological behavior, it's a real bug even without the
> performance loss.
>
> NATE

I hope no-one says reiser4 is "2 times faster than ext3" before this
issue is cleared.
Could some developer (if Nate's one, pardon me) comment on this issue?
It seems to me
much more important than that endless thread about "official point of view".

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.

On kernel-2.6.17.7 currently.

--vk


  reply	other threads:[~2006-08-10 16:36 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 [this message]
2006-08-10 18:48     ` David Masover
2006-08-10 18:55       ` Łukasz Mierzwa
2006-08-10 20:59         ` David Masover
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=44DB6080.8070306@iki.fi \
    --to=vegai@iki.fi \
    --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.