[ Saturday, January 22, 2000 ] Michael wrote:
> > I was wondering if anyone had any experiances or knew of any
> > gotcha's for moving from a 2.0.36 kernel with the
> > raid0145-19990108-2.0.36 patch and raidtools 0.90 to 2.2.14 on a
> > RAID-1 system. Since I have no backups, nor the ability to do any,
> > I'm a bit worried about trashing the filesystems.
>
> I did it last week with 2.0.33 + raidtools 0.42 Was pretty easy. Here
> is my cook book.
Reading over your description, it sounds like you stuck with the
in-kernel (0.4x) raid. Not that it's a bad decision (if it ain't
broke :) but his scenario with will 0.90 raid.
Since he's already 0.90 RAID, all he should need to do is
get the 2.2.14 patch for 0.90 RAID from
http://www.redhat.com/~mingo/raid-2.2.14-B1
and then update his raidtools package to the one from
kernel.org/pub/linux/daemons/raid/alpha/raidtools-19990824-0.90.tar.gz
It's worth emphasizing that since he's used md with the raid0145
patch against 2.0.36 that he's using 0.90 RAID and the 2.2.14
patch will be *necessary* to maintain functioning raid and the
newer raidtools equally necessary.
The recommendation I'd make as well, just to help the paranoia
which is legitimate in a no-backup scenario, is that if this
md array isn't root, add the /etc/fstab mount options so it's
only mounted read-only. This should help reduce any exposure
(not that you should have any following the above instructions)
and he'll be able to look around and make sure the filesystem
looks good before remounting r/w and going "live"
James
--
Miscellaneous Engineer --- IBM Netfinity Performance Development
