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:03:47 +0200 [thread overview]
Message-ID: <E14p0Et-0001Qz-00@sites.inka.de> (raw)
In-Reply-To: <01041521302600.15046@tabby>
In article <01041521302600.15046@tabby> you wrote:
>>a) stop rebuild until fsck is fixed
> And let fsck read bad data because the raid doesn't yet recognize the correct
> one....
a degraded raid will not deliver broken data. and even if it does, one more
reason not to check a degraded raid.
> There is nothing to fix in fsck. It should NOT know about the low level
> block storage devices. If it does, then fsck for EACH filesystem will
> have to know about ALL different raid hardware/software implementations.
fsck does not neet to be changed, yoi can have a shell script loop and check
the raid state before caling the fsck.
>>b) wait with fsck until rebuild is fixed
> Depends on your definition of "fixed"
fixed as in rebuild, thats what we where tlking about, no?
. The most I can see to fix is
> reduce the amount of continued update in favor of updating those blocks
> being read (by fsck or anything else). This really ought to be a runtime
> configuration option. If it is set to 0, then no automatic repair would
> be done.
yes would be a nice feature if rebuild can be made to only to io which is
required by the kernel anyway. since fsck will reach a lot of meta data this
is a fairly good start for a slow rebuild.
Greetings
Bernd
next prev parent reply other threads:[~2001-04-16 4:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9bcoph$1vj$1@ns1.clouddancer.com>
2001-04-15 18:18 ` Linas Vepstas
2001-04-15 19:59 ` Colonel
2001-04-16 1:14 ` Bernd Eckenfels
2001-04-16 2:23 ` Jesse Pollard
2001-04-16 4:03 ` Bernd Eckenfels [this message]
2001-04-16 2:38 ` Jonathan Lundell
2001-04-16 2:51 ` Jesse Pollard
2001-04-16 19:06 ` Jakob Østergaard
2001-04-16 14:16 ` fsck, raid reconstruction & bad bad 2.4.3 + some numbers Francois Romieu
2001-04-17 11:53 ` fsck, raid reconstruction & bad bad 2.4.3 Ookhoi
[not found] <p05100b09b7000a8c3bc9@207.213.214.34>
2001-04-16 4:05 ` Bernd Eckenfels
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=E14p0Et-0001Qz-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
all inboxes | Powered by JetHome®