On Sun, 3 Mar 2002, Neil Brown wrote: > No... the System.map looks like it was the same. > Still, something very odd is going on. > E.G. the COMPLETE RAID STATE PRINTOUT > does not mention md2, but it is md2 that had the error. > > Could you give me a detailed description of your setup: > What raid arrays do you have and how are they configured? > (cat /proc/mdstat might be enough) Have to reboot computer to do that, after OOPS it cat /proc/mdstat blocks. > What exactly did you do to produce the error? raidsetfaulty /dev/md2 /dev/hdi3 > What does /proc/mdstat look like afterwards? > Can't see. It blocks on this procedure after OOPS. One time it didn't OOPS on raidsetafulty I send mdstat after removing and hotadding device in one of previous email (when reconstruction was stucked). lp gody __________________________________________________________________ | Matjaz Godec | Agenda d.o.o. | ISP for business | | Tech. Manager | Gosposvetska 84 | WAN networks | | gody@slon.net | si-2000 Maribor | Internet/Intranet | | tel:+386.2.2340860 | Slovenija | Application servers | |http://www.slon.net |http://www.agenda.si | Caldera OpenLinux | - 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
