Hi,
Note: Could people email me directly please as I am not on the list.
I found the message at the bottom on the mailing list archives...
I'd like to register a "me too" with this problem. Was there any
further discussion?
I've got a 2.2.14 kernel with the Mingo patch 2.2.14-B1, and I get the
same problem. I get no scsi errors, no other kernel messages after the
raid reconstruction starts, and the completion time slowly climbs. This
has happened on a couple of machines now.
There is the possibility that the drive is faulty (its hard to be sure
as there were a few SCSI bus errors that affected a couple of other
devices too before it got removed from the mirror).
#uname -a
Linux fsx.bssssq.edu.au 2.2.14-fsx-20000421 #1 Fri Apr 21 10:26:45 EST
2000 i686 unknown
#cat /proc/mdstat
Personalities : [raid1]
read_ahead 1024 sectors
md0 : active raid1 sdd2[1] sda2[0] 1024960 blocks [2/2] [UU]
md3 : active raid1 sdd3[1] sda3[0] 7846848 blocks [2/2] [UU]
md2 : active raid1 sde1[2] sdb1[1] 35881024 blocks [2/1] [_U]
recovery=28% finish=3168.1min
md1 : active raid1 sdf1[1] sdc1[0] 17775808 blocks [2/2] [UU]
unused devices: <none>
Also can I suggest that whoever maintains this list, creates a
signature/footer to the bottom of every email that contains the mailing
list archive address and the faq/howto?
Any help pointers etc would be most appreciated.
-------------------------
begin previous message:
On Friday, May 26, 2000, Thomas Gebhardt said:
<snip...>
> /proc/mdstat says that the new disk is resyncing but there is no
> progress at all. There is only 1% of the mirror in sync now and
> the estimated time of completion grows continuously. There is
> a load average of about 1.0 caused by this process.
>
I have seen the same thing. 0% reported progress,
time estimate runs away. This after doing 'raidsetfaulty',
'raidhotremove', and 'raidhotadd' on an OK disk partition -
I was just doing some testing.
> After several trys I gave up to resync the mirror and started
> the server with the incomplete RAID 1 Array :-(
>
For me, the only way to stop this was to reboot (raidstop
just hung). Even reboot was not clean as the offending array
wouldn't stop during shut down. Had to press reset - causing
long re-sync of other arrays after restart.
> Environment:
> Kernel is 2.2.10 with new-raid-style patches applied, auto-detection
> activated and a persistent superblock.
>
I saw this with clean 2.2.14, mingo's 2.2.14-B1 patch,
RAIDTOOLS-19990824-0_90_TAR.GZ, autodetect enabled raid
in the kernel (not a module).
> Any hints?
>
> Thanks, Thomas
--
Robert Stuart
Systems Administrator
ph: 3864 0364
