mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <elmer@linking.ee>
To: <arjanv@redhat.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: softraid + serverraid locking FS
Date: Wed, 10 Sep 2003 14:12:08 +0200 (EET)	[thread overview]
Message-ID: <37546.195.80.106.123.1063195928.squirrel@mail.linking.ee> (raw)
In-Reply-To: <1063181415.5021.0.camel@laptop.fenrus.com>


the same problem with vanilla 2.4.22 (SMP kernel on UP hw)

for example, after startup:

1. cp -dpR lotsfiles4GB /testcopy
2. load goes with minutes to 13
3. /bin/sync  blocks
4. Ctrl-Z to cp
5. ps axlef waits 3-10 secs before answer as raid1 sync goes with 14kB/sec

previous problem was without raid sync, currently just it takes time to
test without it
NB! the same copy from the same softraid partition to the same softraid
partition sucks a bit, but load does not grow steadily, remains 3changing raid1sync speed affects a bit the whole thing, but does not end it.

the same copy within serverraid partition is ok.

Currently I havent managed to get softdog into action, but behaviour is
still bad enough to call it a BUG.




> On Wed, 2003-09-10 at 10:52, elmer@linking.ee wrote:
>>  cp -dpR lotsfiles2GB /testcopy
>>
>>                     SMP x335   UP x335
>> serverraid-serverraid  OK          OK
>> softraid-softraid      OK          OK
>> softraid-serverraid    OK          OK
>> serverraid5E-softraid  SLEEPY       X
>> serverraid1E-softraid     X       PROBLEM
>>
>> it is redhat AS 2.4.9-25 kernel, SMP kernel for both.
>
> that kernel is very old and heavily patched; lkml is not the place to
> report problems, your Red Hat support contact is...




      reply	other threads:[~2003-09-10 11:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10  8:52 elmer
2003-09-10  8:10 ` Arjan van de Ven
2003-09-10 12:12   ` elmer [this message]

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=37546.195.80.106.123.1063195928.squirrel@mail.linking.ee \
    --to=elmer@linking.ee \
    --cc=arjanv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®