[OpenAFS] Stopping afsd on Solaris?
Fri, 28 Oct 2005 10:37:30 +0200
* Coy Hile [2005-10-27 12:19:30 -0700]:
> On Thu, 27 Oct 2005, E. Chris Garrison wrote:
> > Thanks for the suggestions, Coy.
> > It doesn't complain about any of those, but the afsd processes are
> > still running and 'modinfo' still shows the module.
> I've seen the same thing here on my systems. When the processes are stuck
> (I think they're waiting for kernel threads or something so they can't be
> killed), the only recourse I've had is to reboot. But, I've also found
> that when I shutdown the client first, then the server using the process
> I listed (though if the machine in question is running both the client and
> server, don't modunload until the end), the afsd processes shutdown.
> One caveat though is that if things are trying to access files in AFS on
> the client while you shutdown the client, the afsd processes won't die.
Precisely. Having recently tried to upgrade OpenAFS on a Solaris 8
test system via the modunload route, I can say that if AFS is in active
use there is a good chance of the modunload approach triggering a
kernel panic. So I prefer to upgrade with a clean reboot instead.
As for the frequency of reboots, I find myself upgrading AFS so rarely
that it isn't a serious issue for me. I normally apply "reboot required"
patches from Sun every three months or so, and am still running OpenAFS
1.2.9 on most Solaris clients (will switch to 1.4.0 in the next round of