Red Hat Bugzilla – Bug 141050
Permission of logical volumes do not allow backup.
Last modified: 2007-11-30 17:10:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Description of problem:
Logical volumes are create as root.root with 600 permissions.
It would be nice if they had similar permissions as regular disks.
That way out of the box amanda would not complain that it does not
have permissions to backup / for instance.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. ls /dev/mapper
Actual Results: brw------- 1 root root 253, 0 Nov 28 08:25 vg00-lvroot
Expected Results: brw-rw---- 1 root disk 253, 0 Nov 28 08:25
umask can be set in the lvm2 config file.
Will think about the best way to incorporate this (distribution-independent)
maybe as a libdevmapper extension configured from the lvm2 config file.
*** Bug 142123 has been marked as a duplicate of this bug. ***
The code currently does:
mknod(path, S_IFBLK | S_IRUSR | S_IWUSR | S_IRGRP, dev)
libdevmapper needs to take uid, gid + custom umask.
Well the other problem is that if you try and add mapper/* for
instance in a udev permissions file, all other files in /dev/mapper
will change permissions, owner and group but not the lv devices.
For now, I'm making the uid,gid, mode compile-time options, so that
each distribution can choose appropriate settings. libdevmapper
interface can then be extended to make the settings per-LV if there's
Fixed in device-mapper CVS; will be included in next release.
Included in 1.00.20
*** Bug 153002 has been marked as a duplicate of this bug. ***
*** Bug 161555 has been marked as a duplicate of this bug. ***