![]() | |||||||||||||
Messages in this thread |
Yeah, that what I thought. I have some more info, that I have uncovered as I rebuild my system. I am using raidtools 0.41 from ftp.kernel.org, is this correct? The md.txt in the kernel docs another site etc. After mke2fs'ing, (creation goes without warnings), I e2fsck'ed, and it gets errors...like the following: Error reading block 2097172 (Success) while doing inode scan, Ignore error<y>? I get these for every block up to 5000000 or so. Also doing a bad block check while making the filesystem gives badblocks: Invalid argument during seek So, I decided to do the same things to the individual hd's that I was making the md0 from. They worked beautifully. No errors, no bad blocks. This is with a freshly compiled 2.1.86 kernel. glibc. Isaac Connor iconnor@uwaterloo.ca On Sun, 8 Mar 1998, Andy Higgins wrote: > > My experience with md raid0 has been a very good one: > > System Dual P-PRO 200 Tyan > 2 BusLogic BT-948's and one md0 device using raid0 > consisting of 6 Seagate 4GB Hawks. > Application: multiple full news feeders and readers.. > I've been testing new News software has lead to almost a crash > a day and fsck cleans up /dev/md0 perfectly with no > file corruption noticeable. Have been running this configuration > with INN for about a 6 mos and have yet to lose any data (knock on wood) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu | ||||||||||||
| Last update: 2005-03-22 12:41 [W:0.916 / U:0.010 seconds] ©2003-2008 Jasper Spaans | |||||||||||||