Re: Few questions

2007-12-07 Thread Corey Hickey
Michael Makuch wrote: I realize this is the developers list and though I am a developer I'm not a developer of linux raid, but I can find no other source of answers to these questions: Don't worry; it's a user list too. $ cat /proc/mdstat Personalities : [raid6] [raid5] [raid4] md0 :

Re: RAID 5: weird size results after Grow

2007-10-13 Thread Corey Hickey
Marko Berg wrote: Bill Davidsen wrote: Marko Berg wrote: Any suggestions on how to fix this, or what to investigate next, would be appreciated! I'm not sure what you're trying to fix here, everything you posted looks sane. I'm trying to find the missing 300 GB that, as df reports, are not

Re: RAID 5: weird size results after Grow

2007-10-13 Thread Corey Hickey
Justin Piszcz wrote: On Sat, 13 Oct 2007, Marko Berg wrote: Corey Hickey wrote: Marko Berg wrote: Bill Davidsen wrote: Marko Berg wrote: Any suggestions on how to fix this, or what to investigate next, would be appreciated! I'm not sure what you're trying to fix here, everything you

Re: Moron Destroyed RAID6 Array Superblocks

2007-04-14 Thread Corey Hickey
Aaron C. de Bruyn wrote: Ok--I got moved in to my new place and am back and running on the 'net. I sat down for a few hours and attempted to write a script to try all possible combinations of drives...but I have to admit that I'm lost. I have 8 drives in the array--and I can output every

Re: 2.6.20: reproducible hard lockup with RAID-5 resync

2007-02-18 Thread Corey Hickey
Neil Brown wrote: Ok, so the difference is CONFIG_SYSFS_DEPRECATED. If that is not defined, the kernel locks up. There's not a lot of code under #ifdef/#ifndef CONFIG_SYSFS_DEPRECATED, but since I'm not familiar with any of it I don't expect trying to locate the bug on my own would be very

Re: 2.6.20: reproducible hard lockup with RAID-5 resync

2007-02-17 Thread Corey Hickey
Corey Hickey wrote: When I get home (late) tonight I'll try running dd and badblocks on the corresponding drives and partitions. Well, I haven't been able to reproduce the problem that way. I tried the following: $ dd id=/dev/hda of=/dev/null $ badblocks /dev/hda $ badblocks -n /dev/hda

Re: 2.6.20: reproducible hard lockup with RAID-5 resync

2007-02-16 Thread Corey Hickey
Neil Brown wrote: On Thursday February 15, [EMAIL PROTECTED] wrote: I think I have found an easily-reproducible bug in Linux 2.6.20. I have already applied the Fix various bugs with aligned reads in RAID5 patch, and that had no effect. It appears to be related to the resync process, and makes

Re: 2.6.20: reproducible hard lockup with RAID-5 resync

2007-02-16 Thread Corey Hickey
Neil Brown wrote: On Thursday February 15, [EMAIL PROTECTED] wrote: I think I have found an easily-reproducible bug in Linux 2.6.20. I have already applied the Fix various bugs with aligned reads in RAID5 patch, and that had no effect. It appears to be related to the resync process, and makes

2.6.20: reproducible hard lockup with RAID-5 resync

2007-02-15 Thread Corey Hickey
I think I have found an easily-reproducible bug in Linux 2.6.20. I have already applied the Fix various bugs with aligned reads in RAID5 patch, and that had no effect. It appears to be related to the resync process, and makes the system lock up, hard. The steps to reproduce are: 1. Be running

Re: RAID5, 2 out of 4 disks failed, Events value differs too much

2006-12-07 Thread Corey Hickey
Bodo Thiesen wrote: Hi, I have a little problem: Some hours ago the second of four disks were kicked out of my RAID5 thus rendering it unusable. As of my current knowledge, the disks are still working correctly (I assume a cable connection problem) but that's not the problem. The real

Re: Odd (slow) RAID performance

2006-12-07 Thread Corey Hickey
Bill Davidsen wrote: Dan Williams wrote: On 12/1/06, Bill Davidsen [EMAIL PROTECTED] wrote: Thank you so much for verifying this. I do keep enough room on my drives to run tests by creating any kind of whatever I need, but the point is clear: with N drives striped the transfer rate is N x base