On Fri, Sep 01, 2006 at 02:32:08AM -0500, Robert Jones wrote:
> All -
>
> I am having issues with filesystem corruption on a RAID1 array using
> RAIDframe on OpenBSD 3.7. If I copy a large (500M+) file onto a
> filesystem on the array, the copied file will end up corrupted, other
> files on the filesystem may end up corrupted and fsck will show various
> errors in the filesystem metadata. The drives themselves check out fine
> and are showing no damaged sectors or other problems. Can anyone help me
> identify and fix the problem?
>
> Contents of /etc/raid0.conf, fdisk info and dmesg are below. I'll
> provide any additional information as necessary.
Disklabel would be useful. Oh, and for the record, upgrade. Not that
that would solve the problem at hand...
> ----
>
> $ cat /etc/raid0.conf
> START array
> 1 2 0
>
> START disks
> /dev/wd1a
> /dev/wd2a
>
> START layout
> 128 1 1 1
>
> START queue
> FIFO 100
That's ok.
> $ sudo fdisk wd1
> Disk: wd1 geometry: 48641/255/63 [781417665 Sectors]
> Offset: 0 Signature: 0xAA55
> Starting Ending LBA Info:
> #: id C H S - C H S [ start: size ]
> ------------------------------------------------------------------------
> 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
> 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
> 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
> *3: A6 0 1 1 - 48640 254 63 [ 63: 781417602 ] OpenBSD
>
> $ sudo fdisk wd2
> Disk: wd2 geometry: 48641/255/63 [781417665 Sectors]
> Offset: 0 Signature: 0xAA55
> Starting Ending LBA Info:
> #: id C H S - C H S [ start: size ]
> ------------------------------------------------------------------------
> 0: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
> 1: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
> 2: 00 0 0 0 - 0 0 0 [ 0: 0 ] unused
> *3: A6 0 1 1 - 48640 254 63 [ 63: 781417602 ] OpenBSD
Ok.
> $ dmesg
> OpenBSD 3.7 (ORBITAL.SP) #1: Wed Jul 27 01:29:04 PDT 2005
> [EMAIL PROTECTED]:/usr/src/sys/arch/i386/compile/ORBITAL.SP
> Kernelized RAIDframe activated
> raid0 (root): (RAID Level 1) total number of sectors is 781417472 (381551
> MB)
> dkcsum: wd0 matched BIOS disk 80
> dkcsum: wd1 had no matching BIOS disk
> dkcsum: wd2 had no matching BIOS disk
> root on wd0a
> rootdev=0x0 rrootdev=0x300 rawdev=0x302
> raid0: Device already configured!
Looks a little fishy here, what are you trying to do? In any case,
/etc/raidX.conf is only required with kernels that do not automount, or
with RAID sets that are not configured to be automounted. I usually
rename them to /etc/raidX.autoconf or similar to keep the configuration
in a logical place while not interfering with normal boot.
Anyway, the most likely issue is some size mismatch - say, a swap space
configured in the same place on the disk as your RAID array. I'd check
all disklabels, including that on raid0, with extreme care.
Joachim
