Re: raid bug in 2.4.20

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2003-04-11T10:20:33,
   Alfred Isele <Alfred.Isele@fujitsu-siemens.com> said:

> After rebooting the resynch really starts.
> Moreover sometimes after detaching (... -f ... -r ...)
> I have either raid1d or mdrecoveryd 
> obviously looping uninterruptible on a CPU. 

Hrm. I've not had that happen to me, but it would be nice if you could provide
sysrq-t output would be helpful.

What happens if you mdadm -S the array? What is the mdadm --detail status?


Sincerely,
    Lars Marowsky-Brée <lmb@suse.de>

-- 
SuSE Labs - Research & Development, SuSE Linux AG
  
"If anything can go wrong, it will." "Chance favors the prepared (mind)."
  -- Capt. Edward A. Murphy            -- Louis Pasteur
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux