On Wed, 2005-09-21 at 19:21 +0200, Bastian Blank wrote:
> reassign 329409 lvms
> severity 329409 wishlist
> tags 329409 wontfix
> merge 329409 316338
> thanks
>
> On Wed, Sep 21, 2005 at 10:18:05AM -0600, Bdale Garbee wrote:
> > It appears that /etc/init.d/lvm creates entries in /dev/mapper
>
> This script calls the appropriate lvm for the kernel.
The code in create_dm_device() makes device nodes with mode 600, owner
and group root. I *think* that's the root cause of my problem. Feel
free to explain why you think the problem is elsewhere if I have
mis-diagnosed the problem.
> > with the
> > wrong
> > group and permissions, which breaks various backup packages including amanda
> > which assume they can use group disk to access the volume.
>
> Why do you assume they are wrong?
With some regularity, I've found that my amanda server is no longer
successfully backing up my main file server's partitions that are using
lvm. I finally had time to investigate this, and the root cause appears
to be that user backup which is in group disk does not have read access
to the volumes in question. That is because all the /dev/mapper/vg*
entries were root, root, 0600, which obviously is wrong. Manually
changing this to root, disk, 0660 solved amanda's problem.
>
> > The correct combination is owner root, group disk, permissions 0660.
>
> Please show me the definition.
I'm the maintainer of the makedev package, and it has created all disk
devices with the following definition for years... thus this is what
users and package maintainers expect:
disk=" root disk 0660"
Any device entries created by lvm should use this same configuration,
and in the past they have. The current package is just inconsistent.
The /etc/devfs/conf.d/50lvm file gets it right:
REGISTER ^vg[0-9]+/.[^/]*$ PERMISSIONS root.disk 0660
Please fix the other place(s) in lvm-common where it's wrong...
Bdale
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
