2 ms·
> Keep in mind a task in `TASK_UNINTERRUPTIBLE` is already sleeping, it's not doing anything. Killing it doesn't change anything or unblock the kernel, it just
by AnIdiotOnTheNet 8y ago
> Keep in mind a task in `TASK_UNINTERRUPTIBLE` is already sleeping, it's not doing anything. Killing it doesn't change anything or unblock the kernel, it just removes the `task` from the scheduler.
....so why can't I force that? When you encounter this problem recovery isn't ever going to happen anyway.
- wyldfire 8y agoIt's already in a state where it can't get back on the run list. The problem isn't that it's going to eat your CPU cycles, the problem is that it's still holding resources that you want it to give back. Taking it out of the process list won't give back those resources, it would just make it so it doesn't show up under `ps`. > When you encounter this problem recovery isn't ever going to happen anyway. The kernel's design can't distinguish between this unrecoverable situation and the normal functionality. Or rather it could, if it had a sane timeout. It doesn't, that's the defect.
- AnIdiotOnTheNet 8y agoAnd there's really no way around that? I find this difficult to believe, but whatever. Guess I just have to live with stuck mounts and other crap.