# Sample raid-0/1 configuration
# setup strip
raiddev /dev/md0
raid-level 0
chunk-size 16
persistent-superblock 1
nr-raid-disks 2
nr-spare-disks 0
device /dev/sda1
raid-disk 0
device /dev/sdb1
raid-disk 1
# second strip
raiddev /dev/md1
raid-level 0
chunk-size 16
persistent-superblock 1
nr-raid-disks 2
nr-spare-disks 0
device /dev/sdc1
raid-disk 0
device /dev/sdd1
raid-disk 1
# start mirror
raiddev /dev/md2
raid-level 1
nr-raid-disks 2
nr-spare-disks 0
chunk-size 128
persistent-superblock 1
device /dev/md0
raid-disk 0
device /dev/md1
raid-disk 1
I didn't change anything about read/write sizes. If the problem is
raid related, this worries me.
Thanks
-jeremy
> It is likely that this is a Raid0 problem and not an NFS problem.
>
> There is a big FIXME in the front of the raid0_map function.
> Are you using the default read/write sizes?
>
> Allen
>
> >>>Jeremy Hansen said:
> >
> > Got an Oops with user land nfsd now, although this just killed
> > nfsd operations. The machine was still very mucy alive otherwise
> > allowing me to properly reboot it.
> >
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.rutgers.edu
> Please read the FAQ at http://www.tux.org/lkml/
>
--------------------------
Y2K. We're all gonna die.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/