Bug 159377

Summary: anaconda prevents the cciss module from unloading
Product: Red Hat Enterprise Linux 4 Reporter: Con Tassios <ct>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED DUPLICATE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-06-07 20:16:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Con Tassios 2005-06-02 04:04:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050519 Firefox/1.0.4

Description of problem:
I use the %pre section in kickstart scripts to create RAID volumes on HP SmartArray controllers using the HP hpacucli utility. In order for the cciss driver to read the new controller configuration, the cciss module must be reloaded.

On RHEL3, an 'rmmod cciss' is successful, but on RHEL4 the module cannot be unloaded because it is in use.  It appears that anaconda is holding this resource preventing cciss from being removed.  The 'Used by' column in lsmod shows the count equivalent to the number of logical drives presented by the controller at bootup.



Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1.rmmod cciss in %pre section of kickstart script
2.
3.
  

Actual Results:  cciss module fails to unload as it is in use

Expected Results:  module should unload.

Additional info:

Comment 1 Jeremy Katz 2005-06-07 19:45:38 UTC
anaconda isn't doing anything to keep devices open.  But rmmod for modules isn't
guaranteed... it's possible that this is occurring within the cciss driver.

Comment 2 Jeremy Katz 2005-06-07 20:16:12 UTC

*** This bug has been marked as a duplicate of 157622 ***