Subject: Re: upgrade from 2.0.2 to 3.0 was [rpc.statd error]
To: sp4rc <email@example.com>
From: Manuel Bouyer <firstname.lastname@example.org>
Date: 01/02/2006 21:29:46
On Mon, Jan 02, 2006 at 08:51:34PM +0100, sp4rc wrote:
> > This is a bug in rpc.statd which corrupts its database when it is shutdown
> > (such as on reboot, or after a /etc/rc.d/nfslocking stop). This has been
> > fixed recently, at last on netbsd-2 and netbsd-3 (NetBSD 3.0 has the fix).
> > Now you have to upgrade your rpc.statd, and delete the /var/db/statd.status
> > file (be carefull if you have NFS client using locks, you'll have to make
> > sure none of them holds a lock when you do this)
> thanks for your answer, I haved stopped nfslocking and the nfsd and
> removed /var/db/statd.status. After restarting the daemons everything
> worked as expected for about 5min...afterwards the following error
> Jan 1 19:37:13 proteus rpc.lockd: no matching entry for hostA
> So instead of updating the nfsd I have decided to upgrade to the latest
> release 3.0, because I would like to enjoy nic-bounding and a stable
> working nfsd.
> As I have already mentioned before, I am running NetBSD 2.0.2 on a
> AS1200 system, with kernelized raidframe enabled and having / on a 2
> disk raid0 mirror. Now I am quite unsure on how to start upgrading. So
> far I have downloaded the Alpha ISO and red throught the INSTALL.html,
> especially through the upgrade section. But there is nothing mentioned
> about how to handle kernelized raidframe systems. I am bit afraid of
> crashing my system...
> I never did an upgrade befor so any hints and help on this topic would
> be greatlly appreciated. Maybee anyone has been in the same situation
> and is willing to share his experience.
Well, the alpha INSTALL kernel doesn't have raidframe, so you can't upgrade
using the install boot media. But this should work:
- install a 3.0 GENERIC kernel (keep a backup of your old kernel) and reboot
- unpack in / all 3.0 tgz binary sets exept etc and xetc
- unpack in /tmp etc.tgz and xetc.tgz, and then run:
/usr/sbin/postinstall -s /etc -d / fix
You can run postinstall as many times as you want. You'll have to fix
some of the problems pointed out by postinstall (such as missing users and
groups) by hand. run postinstall and fix until postinstall doens't report
any failed fix.
- reboot. You should now have a working 3.0 system.
Manuel Bouyer <email@example.com>
NetBSD: 26 ans d'experience feront toujours la difference