Bug 849158

Summary: Named will not shut down after filesystem corruption causes /var to remount read-only.
Product: Red Hat Enterprise Linux 5 Reporter: Moray.Henderson
Component: bindAssignee: Adam Tkac <atkac>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.4CC: ovasik
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-18 13:04:43 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Moray.Henderson 2012-08-17 13:26:35 UTC 
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):
bind-9.3.6-4.P1.el5_4.2

How reproducible:
Always

Steps to Reproduce:
1. Remount /var read-only
2. "service named stop" or "rndc halt" or "kill -TERM <pid>"
3.
  
Actual results:
Stop or halt command hangs; named remains active

Expected results:
named should shut down

Additional info:
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.
Comment 1 Adam Tkac 2013-03-18 13:04:43 UTC 
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.