Hello: I have an application that uses raw Logical Volumes for database storage. In RHEL 5.X when you created a LV it would create a symbolic link in the VG name in /dev that pointed to /dev/mapper. Example1: /dev/vg01/database -> /dev/mapper/vg01-database In RHEL 6.X it now creates a symbolic link in the VG directory pointing to a dm-* name and in /dev/mapper the name points to the same dm-* name. Wxample2: /dev/vg01/database -> ../dm-9 This in itself is not really causing any problems, it was just different. The real problem is the device files need to be owned by the application owner with read and write permission and the group permission need to be read only, which the users of the application will be in. When I do chmod 0644 /dev/vg01/database, it follows the symbolic link and changes /dev/dm-9, and chown appl:appl /dev/vg01/database changes the owner and group. The problem is the first time the application owner opens the device file for writing, the mode, owner and group change back to rw-rw---- and owned by root and group disk. I have tried changing selinux to permissive, but it did not do any good. So is there a way to keep the device file names from changing back automatically? I assume I could relabel them in some way, but I suspect when the systems is rebooted and udev and lvm create the device names again, they will be with the default labeling, mode, owner and group values. ----- Thanks: Jack Allen -- redhat-list mailing list unsubscribe mailto:redhat-list-request@xxxxxxxxxx?subject=unsubscribe https://www.redhat.com/mailman/listinfo/redhat-list