[SOLVED] how to reboot (without pulling the plug)

[dpaddy]

I think I have lots of problems related to nfs, but perhaps the first to solve is: How do I make the command

[NTU]

What does

[dpaddy]

Near as I can tell the machines are frozen ("telinit 0" and "shutdown -r now" have no effect). I guess there is nothing to be done... so I'll pull power chords

I'll interpret your reply as a suggestion to in the future type "telinit 0" or "shutdown -r now" as an alternative to reboot. I am generally cluless -- is "telinit 0" safe as compared with reboot?

[NTU]

Back on my Linux rig again.

The reason your machine won't shut down sounds like it's because OpenRC can't stop the NFS process; stopping services and unmounting filesystems is a required part of the init shutdown service as that's what it does to properly kill whatever processes and applications are loaded in memory; this is to avoid corruption and improper exiting of such things.

Are you using systemd or eudev+OpenRC? Are you able to properly shutdown / restart the server even though that error shows up or does that hang too? What happens if you try to reboot the NFS server without a client connected to it (client is unplugged for example) do you get any errors or hangs on the server?

You really don't want to be unplugging power cords and forcing it to shut-off as this can result in filesystem corruption and/or loss of data.

Hey, one more post and you'll be Tux's lil' helper like me! Congrats!

[szatox]

[dpaddy]

After pulling plugs, I restarted, then put

[NTU]

[dpaddy]

Oh, maybe I'm beginning to understand... I need to learn about

[NTU]

I'm not trying to be rude here so please don't take offense, but if you spent more time learning how to properly set up your init system to handle NFS and mount and unmount properly, you wouldn't need to use Magic SysRq, reboot -f etc, if you're doing any of those things, it isn't a solution. It's a sign something is wrong. Please look over the documentation in the links I posted for handling NFS over fstab (my preferred way) or automount/autofs.

You should never have to do any of the things you're doing in a sane Linux environment. The direction you're taking, tackling your shutdown problem, shouldn't be faced from a "what keys do I press to trigger SysRq" angle.

[dpaddy]

Fair enough, I appreciate the guidance.

[dpaddy]

Magic SysRq key is the answer!

[Hu]

Sysrq is a software alternative to disconnecting the power cable (or holding the power button long enough for the firmware to force power off); it is still an unclean halt used as a workaround for systems that are hung too hard for a normal shutdown. Whenever possible, you should avoid entering a situation where an unclean halt is required.

[gordonb3]

I get this from time to time on ARM systems that don't receive frequent updates. Might be related to using a (crossdev) binhost, or simply because the system fell back further than the devs take into consideration, but running services tend to freeze when trying to write to locations that were removed during the merge. Such changes are usually not obvious and then you'll run into the problem of the system freezing during shutdown.

[krinn]