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 03:14:59 +0200 [thread overview]
Message-ID: <E14oxbX-0000oM-00@sites.inka.de> (raw)
In-Reply-To: <20010415195903.1D0F7683B@mail.clouddancer.com>
In article <20010415195903.1D0F7683B@mail.clouddancer.com> you wrote:
>>(There is no config file to disable/alter this .. no work-around that I
>>know of ..)
> You can't be serious. Go sit down and think about what's going on.
Well, there are two potential solutions:
a) stop rebuild until fsck is fixed
b) wait with fsck until rebuild is fixed
Both of them are valid. The first one is valid in a scenario where you want to
decrease downtimes in favor of insecure operation/or multiple redundancy
The second one is good if you prefer data consitency over small down times. It
might actually speed up the bootup process, one has to measure this.
Greetings
Bernd
next prev parent reply other threads:[~2001-04-16 1:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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-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=E14oxbX-0000oM-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