Bug 160388 - device ownership is reset to defaults following reboot
device ownership is reset to defaults following reboot
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Kernel Maintainer List
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-06-14 16:35 EDT by shawn murphy
Modified: 2007-11-30 17:07 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-06-22 10:59:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description shawn murphy 2005-06-14 16:35:26 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.0.3705)

Description of problem:
I have a RHEL 4 kernel 2.6.9-6.37.EL.  I am installing Oracle which requires that devices be assigned oracle:dba ownership. 

Following a reboot devices assigned to oracle:dba are reset to root:disk ownership.  I have seen this in 2 scenarios: when assigning native sd devices  or bound raw devices.

this forces me to edit my oracle service script to chown on startup. Is this expected behavior?  


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

How reproducible:

Steps to Reproduce:
1. chown oracle:dba /dev/sdt
2. reboot
3. ls -l /dev/sdt (results in root:disk) ownership

Expected Results:  Device ownership assignments should survive reboots

Additional info:
Comment 1 Suzanne Hillman 2005-06-15 13:23:28 EDT
This report looks like a support request. In order to file a support issue,
please either contact Red Hat's Technical Support line at 888-REDHAT-1 or file a
web ticket at http://www.redhat.com/apps/support/.  Bugzilla is not an official
support channel, has no response guarantees, and may not route your issue to the
correct area to assist you.  Using the official support channels above will
guarantee that your issue is handled appropriately and routed to the individual
or group which can best assist you with this issue and will also allow Red Hat
to track the issue, ensuring that any applicable bug fix is included in all
releases and is not dropped from a future update or major release.
Comment 2 Jason Baron 2005-06-21 17:33:04 EDT
I think these would be set 'permanently' via udev. Did our support resolve this
for you? thanks.
Comment 3 shawn murphy 2005-06-22 10:59:08 EDT
Yes changing the ownership in the *.permissions file under /etc/udev worked. 

Note You need to log in before you can comment on or make changes to this bug.