All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artur Makowka <juice@ursynow.2a.pl>
To: reiserfs-list@namesys.com
Subject: Re: Trouble with 2.6.13.4-reiser4-4
Date: Wed, 02 Nov 2005 15:58:45 +0100	[thread overview]
Message-ID: <4368D425.6060109@ursynow.2a.pl> (raw)
In-Reply-To: <43670F5E.9030108@namesys.com>

Hans Reiser napisał(a):

>rvalles wrote:
>
>  
>
>>I've been using reiser4 for a while (since last december). Recently,
>>I've upgraded from 2.6.12 to 2.6.13.4 patched with the reiser4 -4 patch
>>available on the namesys ftp.
>>For some reason, since using this kernel, every now and then the
>>filesystem hits the disk really hard for 15 seconds or so blocking IO
>>for a program or two (I guess those that triggered the problem) and
>>slowing down IO seriously for others. It may be triggered by something
>>as easy as pasting some text from firefox to a xterm running vim, and
>>the text won't get pasted until the HD hitting ends.
>>Just in case, I've booted a recent knoppix and ran the most recent fsck
>>(thank you unionfs and apt-get) on the partition. It fixed some little
>>stuff extents-related that didn't look serious at all. It didn't fix
>>this, tho.
>>Maybe it's worth noting that there are no reiser4 related errors or
>>warnings, nor IO related, on syslog.
>>I can provide more debug-related information on request. I'm looking
>>forward for a patch against plain 2.6.14 (not -mm, that breaks stuff I
>>need and is by itself far too unstable for my taste) to see if it fixes
>>anything, too.
>>Cheers.
>> 
>>
>>    
>>
>We have a patch coming out any day now that will be a lot more stable
>than what is currently the latest.
>
>Vitaly, please label our latest as not very stable in the meantime.
>
>hans
>
>.
>
>  
>
I have to agree with rvalles, as i also noticed very high LA and im 
using latest reiser4 patch with 2.6.13.4 kernel. this is becouse of high 
the I/O usage. I didnt know its reiser4 fault, but it seems logical ( 
other process are waiting for I/O and thats why so high LA )

becouse my machine had already high load anyways, so together with this 
bug it caused few crashes, so im just wondering - how soon there is 
going to be new patch, and is this issue already solved or beign worked on ?

i know the patch will be ready when its ready ;) but i have free hosting 
server and until its resolved i cant turn on all services.

Also, there is nothing strange in logs. Also i have to say one good 
thing about reiser4 - i had many crashes, some becouse of this bug, some 
becouse server has very high load anyways, and reiser didnt delete or 
corrupted even one file durning that. And i had to run --build-fs only 
once or twice.

  reply	other threads:[~2005-11-02 14:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20051101015551.GA1059@148.Red-217-126-33.pooles.rima-tde.net.>
2005-11-01  6:46 ` Trouble with 2.6.13.4-reiser4-4 Hans Reiser
2005-11-02 14:58   ` Artur Makowka [this message]
2005-11-01  1:55 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=4368D425.6060109@ursynow.2a.pl \
    --to=juice@ursynow.2a.pl \
    --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.