Messages in this thread | | | From | Bernd Eckenfels <> | Subject | Re: fsck, raid reconstruction & bad bad 2.4.3 | Date | Mon, 16 Apr 2001 03:14:59 +0200 |
| |
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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |