Re: Incative RAID5 (it should be active)

2006-08-12 Thread Jacob Madsen
Hey again here is some additional information: # mdadm --examine /dev/sda10 /dev/sdb10 /dev/sdc10 /dev/sdd10 /dev/sda10: Magic : a92b4efc Version : 00.90.00 UUID : fc549abf:0e1662f3:3b60b5c3:7a8e6fc7 Creation Time : Tue Oct 19 20:27:43 2004 Raid Level : raid5 De

Incative RAID5 (it should be active)

2006-08-12 Thread Jacob Madsen
Hey I only have 4 sata slots in my computer and i have a raid5 array of partitions on those 4 disks. Today i needed a free sata slots, so i unplugged one of the disks and booted with knoppix. I then did some work, turned of the computer and plugged in the disk again. I should say that i di

Ajak Keluarga Nikmati Perbualan PERCUMA bersama 2000 Jemaah seluruh Negara.!

2006-08-12 Thread Pekida Prihatin
Bismillah hirrohman nirrohim... Assalamualaikum Saudara/Saudari, Apa khabar Saudara/Saudari sekeluarga? semoga sihat-sihat selalu, Saya MAIZATUL BINTI RAHIM, mewakili pekida R&D dan Prihatin Services mengirim email ini kepada Saudara/Saudari untuk menyampaikan satu berita besar. SATU BERI

Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4

2006-08-12 Thread Michael Tokarev
Justin Piszcz wrote: > Is there a doc for all of the options you can echo into the sync_action? > I'm assuming mdadm does these as well and echo is just another way to > run work with the array? How about the obvious, Documentation/md.txt ? And no, mdadm does not perform or trigger data integrity

Re: [bug?] raid1 integrity checking is broken on 2.6.18-rc4

2006-08-12 Thread Justin Piszcz
On Sat, 12 Aug 2006, Chuck Ebbert wrote: Doing this on a raid1 array: echo "check" >/sys/block/md0/md/sync_action On 2.6.16.27: Activity lights on both mirrors show activity for a while, then the array status prints on the console. On 2.6.18-rc4 + the below patch:

Re: Resize on dirty array?

2006-08-12 Thread Tuomas Leikola
On 8/9/06, James Peverill <[EMAIL PROTECTED]> wrote: I'll try the force assemble but it sounds like I'm screwed. It sounds like what happened was that two of my drives developed bad sectors in different places that weren't found until I accessed certain areas (in the case of the first failure)