Hi Linas Vepstas,
(nice name ;-)
> First problem: In kernel-2.4.2 and earlier, if the machine is not cleanly
> shut down, then upon reboot, RAID reconstruction is automatically started.
> (For RAID-1, this more-or-less ammounts to copying the entire contents
> of one disk partition on one disk
On Sun, Apr 15, 2001 at 09:51:52PM -0500, Jesse Pollard wrote:
...
>
> If I've got the numbering right;
> 0 - concatenated stripes => no sync required
> 1 - mirrored => resync required
> a: which drive has the correct info?
a: there are timestamps in the superblocks. o
Linas Vepstas <[EMAIL PROTECTED]> écrit :
[...]
> I want to report a trio of raid-related problems. The third one is
> very serious, and effectively prevents 2.4.3 from being usable (by me).
>
[...]
> The problem: this dramatically slows fsck after an unclean shut-down.
> You can hear the driv
In article <[EMAIL PROTECTED]> 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 differen
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.
> T
At 9:23 PM -0500 2001-04-15, Jesse Pollard wrote:
> >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
On Sun, 15 Apr 2001, Bernd Eckenfels wrote:
>In article <[EMAIL PROTECTED]> 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
In article <[EMAIL PROTECTED]> 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
In list.kernel, linas wrote:
>
>First problem: In kernel-2.4.2 and earlier, if the machine is not cleanly
>shut down, then upon reboot, RAID reconstruction is automatically started.
>(For RAID-1, this more-or-less ammounts to copying the entire contents
>of one disk partition on one disk to anoth
9 matches
Mail list logo
