T.R | Title | User | Personal Name | Date | Lines |
---|
788.1 | clean stop ? | BRSDVP::DEVOS | Manu Devos NSIS Brussels 856-7539 | Thu May 01 1997 08:13 | 11 |
| If LSM is re-synchronizing volumes, this is because these volumes have
not been cleanly stopped at the shutdown time. So, something is not
correct in the way you shutdown the system. Are you using init 0 which
stops everything cleanly or some more abrupt command (like halt,
reboot, shutdown -r ).
So, tell us how you reboot the system and if you stop the application
using the HSZ disks
Manu
|
788.2 | We tried both shtdown -h & shutdown -r | PRCFS1::SOCHUNWAH | | Thu May 01 1997 23:07 | 13 |
|
Hello,
We had tried both "shutdown -h" and "shutdown -r" and have the same
results.
We'll try "init 0" next time to see any different, but because next
two days is holiday. Probably the test will be performed next Monday,
and will update the results here.
SO
|
788.3 | | BRSDVP::DEVOS | Manu Devos NSIS Brussels 856-7539 | Fri May 02 1997 16:39 | 9 |
| So,
You should use "init 0" and not hte old Ultrix "shutdown -r".
Init 0 is running the scripts in /sbin/rc0.d which is stopping
everything.
Manu
|
788.4 | Now I'm confused... | DYOSW5::WILDER | Does virtual reality get swapped? | Mon May 05 1997 08:32 | 10 |
| Well, I'm confused....I have seen notes stating that you shout use init
S, init 0, AND shutdown -r. Maybe engineering can give us a definite
answer.
What is the CORRECT way to shut down a cluster system and re-boot it?
Thanks,
/jim
|
788.5 | | BRSDVP::DEVOS | Manu Devos NSIS Brussels 856-7539 | Mon May 05 1997 14:12 | 19 |
| Jim,
I understand your confusion...
At the beginning (V1.0) ASE requested "shutdown -h".
Now, ASE is really happy with "init 0" which properly run the service
stop script(s) and stop the ASE daemons and AM Kernel driver.
LSM also is needing "init 0" to allow the "clean stop" of all volumes.
A volume which has not been stopped before the reboot will be
resynchronised.
And about the "init s, init 0 ", maybe you are referring to a note for
the Trucluster software, which explained that we cannot use the
command "init s" followed by "init 3" because the member will NOT join
the cluster properly.
Manu. (Not from Engineering:-)
|