this post was submitted on 29 Oct 2024
762 points (94.8% liked)

linuxmemes

21282 readers
1138 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
  •  

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't fork-bomb your computer.

    founded 1 year ago
    MODERATORS
     

    Yes yes, I REALLY want to terminate that process and I am very sure about it too, ty.

    you are viewing a single comment's thread
    view the rest of the comments
    [–] WhyJiffie@sh.itjust.works 16 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

    on windows a process can get in a state so that it is impossible to make it go away, even with process explorer or process hacker. mostly this also involves the bugged software becoming unusable.

    I encounter such a situation from time to time. one way it could happen is if the USB controller has got in an invalid state, which one of my pendrives can semi-reliably reproduce. when that happens, any process attempting to deal with that device or its FS, even the built-in program to remove the drive letter, will stop working and hang as an unkillable process.

    [–] zea_64@lemmy.blahaj.zone 28 points 2 weeks ago (2 children)

    Linux has that issue too. A process in an uninterruptible blocking syscall stays until that syscall finishes, which can be never if something weird's going on.

    [–] WhyJiffie@sh.itjust.works 3 points 2 weeks ago

    oh, that's good to know! iirc that's the same reason it happens on windows too

    [–] WhyJiffie@sh.itjust.works 1 points 2 weeks ago

    oh, that's good to know! iirc that's the same reason it happens on windows too

    [–] bjoern_tantau@swg-empire.de 13 points 2 weeks ago* (last edited 2 weeks ago) (2 children)

    I've seen that on Linux as well. Funnily enough also with faulty file systems. I think NFS with spotty wifi for one.

    Oh, and once with a dying RAID controller. That was a pain in the ass. At that point I swore to only ever do RAID in software.

    [–] WhyJiffie@sh.itjust.works 3 points 2 weeks ago

    oh yeah now that you say, SMB/CIFS mounted share if connection is no more. when I experienced this, it was temporary though, because there's a timeout which is half (or double?) of the configurable reconnection timeout. but now that I think of it, I'm not sure if it made it unkillable.

    [–] greyfox@lemmy.world 1 points 2 weeks ago

    Add a -f to your umount and you can clear up those blocked processes. Sometimes you need to do it multiple times (seems like it maybe only unblocks one stuck process at a time).

    When you mount your NFS share you can add the "soft" option which will let those stuck calls timeout on their own.