I'm seeing a very odd problem on an older installation (3.6) that until now has been working perfectly.
A process on the box stopped responding and could not be killed, so we tried to use the reboot command to reboot the box. The reboot command just hangs and cannot be interrupted.
If I log in via a separate ssh session, I can use ps and see that the reboot command is sitting there in the process table (multiple times now), but it cannot be killed either.
I saw something sort of like this once before. That time I was running a disk load test on the box and reboot typed while the load test was running would not return. Once the load test was killed, reboot would complete. Not sure this is related though, nothing that was running should have been accessing the file system other than having a log file open (but not growing) in /tmp.
I am under the impression that the busybox reboot command really just tells init to do a restart. According to the inittab file that should run rc.shutdown (which checks with what usually happens). This time around, the system never seemed to get to the running rc.shutdown point.
Any thoughts? This particular box is located an hour away from anyone, and although someone was able to drive out and restart it, I'm catching some grief that anyone had to.