> Manuel Bouyer wrote:
>
> However, because of a problem with swap on raidframe, I would make one raid
> for a+b and a second for everything else (this is how I setup my systems
> these days). The problem is that the swap partition isn't closed on
> halt/reboot, so the raid is dirty on next boot and it rebuilds parity.
[...]

The swap-on-raid problem is very easy to overcome.  In fact, it is
specifically listed in the abbreviated netbsd 1.5.3 -> 1.6 changelog.

Put a line like this in your rc.conf:
swapoff=YES		# Remove block-type swap partitions upon shutdown

Fyi, I use swap on a rather large raid1, and things work great.

Actually, my fstab says:
/dev/raid0b	none	swap	sw		0 0
/dev/sd0b	none	swap	sw,priority=2		0 0
/dev/sd1b	none	swap	sw,priority=1		0 0
#/swapfile	none	swap	sw		0 0

And so I wonder if sd0 or sd1 fails and I don't have anything paged to
those disks at all, would it still kernel panic my system??..  Humm..

Fyi.. In netbsd 1.5.x, there was no officially sanctioned fix, but it was
still easy to do.  You would modify /etc/rc.d/swap1 and ... I forget
exactly what you do. I think you would add a statement to the REQUIRE
line..  I found the fix on the mailing lists, and it was a very small
change, tho I never would have figured it out on my own.