Thanks for all that noted the 8192 chunksize was a bit excessive ;-)
The current value (for a postgresql 6.4.2 site) is now 8 (for 8kb)
I am using a linux 2.2.1 "stock" kernel from ftp.ca.kernel.org. I tried applying
the latest raid0145 patch but it failed in many places so I assumed that it was
already "rolled into 2.2.1". Is this correct? FYI: I tried the
raid0145-19990128-2_2-1-devfs-v90.gz patch but there were failures applying it. I
can run it again and list them if it's supposed to work. Another poster (Paul
Jakma) said that the latest 2.2.0 raid-0145 applies perfectly so I'll also try
that.
Another poster indicated that perhaps the partitions where not Linux native (83).
I'll use fdisk tomorrow and confirm this. It's possible since the PC had NT on it
originally.
Summing up.
1. Confirm that all three partitions are Linux native (83) type.
2. Try the last 2.2.0 raid-0145 patch on the 2.2.1 kernel tree.
STeve
[EMAIL PROTECTED]
-----EOT
Evgeny Stambulchik wrote:
> Stephen Hurrell <[EMAIL PROTECTED]> wrote:
>
> > org04:~# mkraid -V
> > mkraid version 0.90.0
> > org04:~# mkraid /dev/md0
> > handling MD device /dev/md0
> > analyzing super-block
> > disk 0: /dev/sda3, 6417967kB, raid superblock at 6417856kB
> > disk 1: /dev/sdb4, 6417967kB, raid superblock at 6417856kB
> > disk 2: /dev/sdc4, 6417967kB, raid superblock at 6417856kB
> > mkraid: aborted
>
> Is your kernel patched with a relevant raid0145-* patch? I've seen the "mkraid:
> aborted" message when (by a mistake) rebooted to a stock kernel, supposed to
> work with raid 0.36.
>
> Regards,
>
> Evgeny
