Red Hat Bugzilla – Bug 849158
Named will not shut down after filesystem corruption causes /var to remount read-only.
Last modified: 2013-04-30 19:52:16 EDT
Description of problem:
named will not shut down cleanly if /var partition has been remounted read-only (e.g. after filesystem corruption detected).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Remount /var read-only
2. "service named stop" or "rndc halt" or "kill -TERM <pid>"
Stop or halt command hangs; named remains active
named should shut down
All other daemons and services accessing /var can be stopped with service(8), although of course they complain they can't remove their /var/run or /var/lock files. Only named requires a "kill -9". If this causes the full OS shutdown process to hang, then it may prevent support personnel accessing the server remotely to try to fix it.
Since RHEL 5 is now in production phase 2 (only important/critical bugs are fixed) and this is not important issue, I'm closing this bug.