One of my co-worker approached me today with a weird problem. Yesterday he had a disk in a 900GiB array failing which he replaced. After that, he run a rebuild/verification, fsck’ed the file system and tried to mount the volume again.
Apparently the mount produced a kernel oops (guess what, the 900GiB is running reiserfs), thus leaving the kernel tainted (or what do they call it ?). So he tried to reboot the box but it didn’t reboot. It started rebooting but then hung (as in not continuing the reboot). He tried to ssh back to the box, and it worked just fine.
This is where sysrq comes in handy.
|
1 2 3 4 5 6 |
# This is gonna activate the sysrq echo 1 > /proc/sys/kernel/sysrq # Now, since we ain't at a console, we can't use the sysrq keys # ("b" for reboot, "o" for shutdown) echo b > /proc/sysrq-trigger |
That’ll restart the box, and cha-ching .. 😀