Following up to my previous post, here is the config for the RAID array that I just can't keep living:
------- 8< ------- cranx:~# cat /etc/raidtab raiddev /dev/md1 raid-level 1 nr-raid-disks 2 nr-spare-disks 0 chunk-size 4 persistent-superblock 1 device /dev/hda2 raid-disk 0 device /dev/hdc2 raid-disk 1 cranx:~# fdisk -l /dev/hda Disk /dev/hda (Sun disk label): 16 heads, 255 sectors, 19156 cylinders Units = cylinders of 4080 * 512 bytes Device Flag Start End Blocks Id System /dev/hda1 0 20 40800 83 Linux native /dev/hda2 21 18665 38033760 83 Linux native /dev/hda3 0 19156 39078240 5 Whole disk /dev/hda4 18666 19156 999600 83 Linux native cranx:~# fdisk -l /dev/hdc Disk /dev/hdc (Sun disk label): 16 heads, 255 sectors, 19156 cylinders Units = cylinders of 4080 * 512 bytes Device Flag Start End Blocks Id System /dev/hdc1 0 20 40800 83 Linux native /dev/hdc2 21 18665 38033760 83 Linux native /dev/hdc3 0 19156 39078240 5 Whole disk /dev/hdc4 18666 19156 999600 83 Linux native cranx:~# cat /proc/mdstat Personalities : [raid0] [raid1] md1 : active raid1 hdc2[1] hda2[0] 38033664 blocks [2/2] [UU] ------- >8 ------- If I set up a brand new filesystem on /dev/md1, mount it, write a bunch of data to it (in this case, a copt of my root filesystem), umount it, then fsck it, 9 times out of ten I get "illegal blocks", and once I got something about a bad filename on /usr/include/linux/[somethingorother]. Basically, the FS is being corrupted in record time. No errors are thrown in dmesg, no oopses, no nothing. Just silent corruption. Any ideas? ... Adam Conrad -- backup [n] (bak'up): The duplicate copy of crucial data that no one bothered to make; used only in the abstract. 1024D/C6CEA0C9 C8B2 CB3E 3225 49BB 5ED2 0002 BE3C ED47 C6CE A0C9