3 ms·
Which is a very good practice if you're in control of the software receiving the error. But so much freaking software doesn't handle this correctly it's maddeni
by Spivak 7y ago
Which is a very good practice if you're in control of the software receiving the error. But so much freaking software doesn't handle this correctly it's maddening and so sleep everything that touches it is the only safe thing to do.
- GauntletWizard 7y agoFor some network filesystems, I want to mount them "Kill every process with a filehandle open to this on error". Is there a way to do that?
- the8472 7y agoNFS has been converted to to the TASK_KILLABLE mentioned elsewhere in the comments, so you could scan for threads stuck in this state, scan proc for open file descriptors pointing to the network filesystems and then kill those processes. That of course doesn't work if you're dealing with a filesystem that still uses TASK_UNINTERRUPTIBLE