Messages in this thread | | | From | Jesse Pollard <> | Subject | Re: fsck, raid reconstruction & bad bad 2.4.3 | Date | Sun, 15 Apr 2001 21:23:27 -0500 |
| |
On Sun, 15 Apr 2001, Bernd Eckenfels wrote: >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
And let fsck read bad data because the raid doesn't yet recognize the correct one....
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.
>b) wait with fsck until rebuild is fixed
Depends on your definition of "fixed". 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.
------------------------------------------------------------------------- Jesse I Pollard, II Email: jesse@cats-chateau.net
Any opinions expressed are solely my own. - 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/
| |