RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 463271 - LVM2, not possible to define owner, group and permissions of a logical volume
Summary: LVM2, not possible to define owner, group and permissions of a logical volume
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: lvm2
Version: 6.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Peter Rajnoha
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-09-22 19:34 UTC by Horacio RM
Modified: 2018-11-14 16:19 UTC (History)
14 users (show)

Fixed In Version: lvm2-2.02.56-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-15 14:32:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Horacio RM 2008-09-22 19:34:37 UTC 
Description of problem:
In the activation process of a logical volume, several
nodes are created in /dev. These are the nodes:
   - /dev/mapper/VGxxxx/LVyyyy
   - /dev/VGxxxx (directory)
   - /dev/VGxxxx/LVyyyy (a symbolic link to /dev/mapper/....)

The problem is that there are applications (databases for 
example) that run under specific users that need access
to the disks directly to store information.

Because (for security reasons) the database runs under other
than root user, there is a need to chown the devices in order
to grant the access to the data.

Well, there are some active environments (for example the cluster
suite) that activates/deactivates the LVs dynamically. 

Currently there is no way to set the OWNER, GROUP and MODE (like
un udev rules) with the Logical Volume Manager, and this functionality
is needed in order to grant access to block devices for specific users.

How reproducible:
Very reproducible.
- Activate a logical volume (if it is not active already).
- Change user/group
- Deactivate it
- Activate it again.
- Check that the user/group has been lost.
And there isn't a way to define this in lvm.con nor udev-rules.

Additional info:
Comment 1 Petr Rockai 2009-03-01 13:43:26 UTC 
I suppose this will be addressed with moving the node creation responsibility to udev, as planned for future LVM versions. I am not sure it is worth addressing separately before that move? Maybe others could comment though...
Comment 2 Peter Rajnoha 2009-03-02 07:35:34 UTC 
Yes, exactly. This will be solved by moving to udev which is on its way out right now... So I expect it to be in upstream in near near future if all goes well. This should replace the old code responsible for creating the /dev contents altogether then.
Comment 3 Dave Wysochanski 2009-03-11 00:37:34 UTC 
Is the plan for RHEL6?
Comment 6 Peter Rajnoha 2009-09-22 13:54:03 UTC 
Udev support has been integrated into device-mapper/lvm2 lately and it's been configured in Fedora rawhide (device-mapper-1.02.37-3, lvm2-2_02_52-3). This provides a start point for inclusion in RHEL6 (we will see later if this is going to be backported back to RHEL5).
Comment 7 Peter Rajnoha 2009-10-08 11:52:43 UTC 
Unfortunately, udev support was switched off again in rawhide due to problems found in anaconda installer. Further analysis shows that the problem was in "parted" utility only that could not deal with new node/symlink layout for DM devices in /dev.

A quick workaround (but rather inefficient) was made to deal with this problem from libdevmapper side. Also, a team of people responsible for "parted" were notified to correct a part of their code where some assumptions were made about DM names and their use while calling dm library functions. We recommended them to correct this and it seems this will be corrected in parted upstream as well soon.

Since this is the only major problem found, we still think about the inclusion of the udev support in RHEL6 (if there are no other obstacles).
Comment 10 Peter Rajnoha 2009-12-21 09:56:40 UTC 
Udev support enabled in lvm2-2_02_56-1_el6.

Permissions for each LV (and for DM devices in general) could be set by udev rules directly, see also doc/device-mapper-1.02.40/12-dm-permissions.rules.
Comment 13 releng-rhel@redhat.com 2010-11-15 14:32:14 UTC 
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.
Note You need to log in before you can comment on or make changes to this bug.