From: Bernd Eckenfels <W1012@lina.inka.de>
To: linux-kernel@vger.kernel.org
Subject: Re: fsck, raid reconstruction & bad bad 2.4.3
Date: Mon, 16 Apr 2001 06:05:03 +0200 [thread overview]
Message-ID: <E14p0G7-0001Sa-00@sites.inka.de> (raw)
In-Reply-To: <p05100b09b7000a8c3bc9@207.213.214.34>
In article <p05100b09b7000a8c3bc9@207.213.214.34> you wrote:
> Is this a pathological case because of the way fsck does business, or does the RAID re-sync affect any disk-bound process that severely?
i gues the seeks are the problem. fsck will quite heavyly reposition, so does
the rebuild, most likely on different ends of the disk.
Greetings
Bernd
next parent reply other threads:[~2001-04-16 4:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <p05100b09b7000a8c3bc9@207.213.214.34>
2001-04-16 4:05 ` Bernd Eckenfels [this message]
2001-04-15 18:18 fsck, raid reconstruction & bad bad 2.4.3 Linas Vepstas
[not found] ` <9bcoph$1vj$1@ns1.clouddancer.com>
2001-04-15 19:59 ` Colonel
2001-04-16 1:14 ` Bernd Eckenfels
2001-04-16 2:23 ` Jesse Pollard
2001-04-16 2:38 ` Jonathan Lundell
2001-04-16 2:51 ` Jesse Pollard
2001-04-16 19:06 ` Jakob Østergaard
2001-04-16 4:03 ` Bernd Eckenfels
2001-04-17 11:53 ` Ookhoi
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=E14p0G7-0001Sa-00@sites.inka.de \
--to=w1012@lina.inka.de \
--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