On Thu, 14 Oct 1999, Tom Livingston wrote:
> Florian Lohoff wrote:
> > I did a bit further - Hung the machine - Couldnt log in (All Terms
> > hang immediatly) - Tried to reboot and when it hung at
> > "Unmounting file..."
> > i got a term SysRq- Tand saw many processes stuck in the D state.
> >
> > Seems something produces a deadlock (ll_rw_blk ?) and all processes
> > trying to access disk get stuck.
>
> Can you duplicate this using only one of the raid5 sets? I tried to cause
> the same behvior with a single raid5 set and it worked fine... but I did not
> layer raid on raid, perhaps this is where the issue is?
When working with a 5 x 18G RAID5 (0 spare) using 2.2.12SMP +
raid 2.2.11 (compiled in, not modules) I would get a endless stream
about buffers when trying to mount the device, mke2fs and e2fsck
worked fine. Seemed to happen when the array was in the beginning of
the reconstruct.
With 2.2.13pre15SMP + raid 2.2.11 I managed to get this a
couple times, but only if I mount it right after reconstruct starts on
a just mkraided array. If I wait till the reconstruct hits 2 - 3 % it
mounts just fine. I have not seen this on arrays smaller than 50G
(but this is not hard data, it could just be the faster reconstruct).
---
As folks might have suspected, not much survives except roaches,
and they don't carry large enough packets fast enough...
--About the Internet and nuclear war.
