reupload because i mixed up sigterm and sigkill like a dumb fuck

you are viewing a single comment's thread
view the rest of the comments
[–] 61 points 5 months ago (6 children)

( 1min 59s / 2 mins )

...

( 2 mins / 3 mins )

???

  • source
  • parent
  • hideshow 6 child comments
  • [–] 45 points 5 months ago (4 children)
  • [–] 16 points 5 months ago* (3 children)

    In those cases there's an easy solution.

    Step 1: sigh

    Step 2: press the power button 5 or 10 seconds while contemplating why you decided to do a quick restart instead of keeping the session and do something actually productive

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 5 months ago (2 children)

    I recommend starting with SysRq+E before that, there's a chance it gets whatever the shutdown was waiting for. And if that fails... REISUB my beloved.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 5 months ago (1 child)

    RSEIUB. Raising skinny elephants is utterly boring.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 4 points 5 months ago

    I might be missing something, but the order I know and have always seen recommended is REISUB. Terminating processes might write data to disk, so it seems to me like you should sync after, not before. Though this is also generally unimportant with modern filesystems and storage media.

  • source
  • parent
  • [–] 16 points 5 months ago

    That's because it first send sigterm, then sigkill. Then it gives up and let the kernel handle it...

    Happens on my BTRFS disk's unmount. If the kernel is currently busy handling some heavy btrfs command (like a 4tb scrub), systemd cannot stop it with sigkill.

    So when it eventually gives up, you also need to wait for the kernel to finally stop the operation and actually disconnect the disk.

  • source
  • parent