Bug#329409: marked as done (group and perms wrong in /dev/mapper)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#316883: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: lvm-common Version: 1.5.17 Severity: important It appears that /etc/init.d/lvm creates entries in /dev/mapper with the wrong group and permissions, which breaks various backup packages including amanda which assume they can use group disk to access the volume. The correct combination is owner root, group disk, permissions 0660. Bdale ---End Message--- ---BeginMessage--- Source: devmapper Source-Version: 2:1.02.07-1 We believe that the bug you reported is fixed in the latest version of devmapper, which is due to be installed in the Debian FTP archive: devmapper_1.02.07-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz devmapper_1.02.07-1.dsc to pool/main/d/devmapper/devmapper_1.02.07-1.dsc devmapper_1.02.07.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz dmsetup-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb dmsetup_1.02.07-1_amd64.deb to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb libdevmapper-dev_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb libdevmapper1.02-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb libdevmapper1.02_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank [EMAIL PROTECTED] (supplier of updated devmapper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 10 Jun 2006 21:20:43 + Source: devmapper Binary: dmsetup libdevmapper1.02-udeb libdevmapper1.02 libdevmapper-dev dmsetup-udeb Architecture: source amd64 Version: 2:1.02.07-1 Distribution: unstable Urgency: low Maintainer: Debian LVM Team [EMAIL PROTECTED] Changed-By: Bastian Blank [EMAIL PROTECTED] Description: dmsetup- The Linux Kernel Device Mapper userspace library dmsetup-udeb - The Linux Kernel Device Mapper userspace library (udeb) libdevmapper-dev - The Linux Kernel Device Mapper header files libdevmapper1.02 - The Linux Kernel Device Mapper userspace library libdevmapper1.02-udeb - The Linux Kernel Device Mapper userspace library (udeb) Closes: 316883 329409 341901 342455 Changes: devmapper (2:1.02.07-1) unstable; urgency=low . * New upstream version. * Update priorities to match overrides. * Acknowledge NMU. (closes: #316883, #329409, #341901, #342455) Files: 4d3f3baac4e84bce0b7484503364c960 762 admin optional devmapper_1.02.07-1.dsc ed0ff12decdc617d9268f213ed2c1d29 923619 admin optional devmapper_1.02.07.orig.tar.gz 4a01f14aaf585cbfb8e7d2a88f03ac47 44831 admin optional devmapper_1.02.07-1.diff.gz f6776d113347ee10fb43744f88fd5f45 51844 libdevel optional libdevmapper-dev_1.02.07-1_amd64.deb b00e5a071a951a26d10f809504b2881b 41058 libs required libdevmapper1.02_1.02.07-1_amd64.deb 1cdc69ffa8c9ce18f5a9db68dca4c931 29196 debian-installer optional libdevmapper1.02-udeb_1.02.07-1_amd64.udeb 225df1b21e94d9f7694446487a5773d6 27394 admin optional dmsetup_1.02.07-1_amd64.deb a861d35324f707a1ea14d6f088751242 13074 debian-installer optional dmsetup-udeb_1.02.07-1_amd64.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iEYEARECAAYFAkSLOIAACgkQLkAIIn9ODhGnGACg7ja7KFaiaKc6LsS60IHoM4OR bycAoNWw4m0c4VxK3SRZYMxQt2bCc0bz =6Bno -END PGP SIGNATURE- ---End Message---
Bug#316883: marked as done (lvm2: creates device nodes as root:root 600, breaking amanda)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#316883: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: lvm2 Version: 2.01.12-2 Severity: normal Hi, unlike lvm10 (which created LV device nodes as root:disk 660), lvm2 creates its device nodes as root:root 600: brw--- 1 root root 253, 1 Jul 4 11:32 vg0-usr This precludes amanda backups from happening. Please deliver lvm2 in a way that makes the LV device nodes readable by group disk. If this can be done, please tell me how to change my local configuration to make backup possible again. Greetings Marc -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.9-zgserver Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages lvm2 depends on: ii debconf 1.4.51 Debian configuration management sy ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libdevmapper1.012:1.01.03-1 The Linux Kernel Device Mapper use ii lvm-common 1.5.19 The Logical Volume Manager for Lin lvm2 recommends no packages. -- debconf information excluded ---End Message--- ---BeginMessage--- Source: devmapper Source-Version: 2:1.02.07-1 We believe that the bug you reported is fixed in the latest version of devmapper, which is due to be installed in the Debian FTP archive: devmapper_1.02.07-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz devmapper_1.02.07-1.dsc to pool/main/d/devmapper/devmapper_1.02.07-1.dsc devmapper_1.02.07.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz dmsetup-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb dmsetup_1.02.07-1_amd64.deb to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb libdevmapper-dev_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb libdevmapper1.02-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb libdevmapper1.02_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank [EMAIL PROTECTED] (supplier of updated devmapper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 10 Jun 2006 21:20:43 + Source: devmapper Binary: dmsetup libdevmapper1.02-udeb libdevmapper1.02 libdevmapper-dev dmsetup-udeb Architecture: source amd64 Version: 2:1.02.07-1 Distribution: unstable Urgency: low Maintainer: Debian LVM Team [EMAIL PROTECTED] Changed-By: Bastian Blank [EMAIL PROTECTED] Description: dmsetup- The Linux Kernel Device Mapper userspace library dmsetup-udeb - The Linux Kernel Device Mapper userspace library (udeb) libdevmapper-dev - The Linux Kernel Device Mapper header files libdevmapper1.02 - The Linux Kernel Device Mapper userspace library libdevmapper1.02-udeb - The Linux Kernel Device Mapper userspace library (udeb) Closes: 316883 329409 341901 342455 Changes: devmapper (2:1.02.07-1) unstable; urgency=low . * New upstream version. * Update priorities to match overrides. * Acknowledge NMU. (closes: #316883, #329409, #341901, #342455) Files: 4d3f3baac4e84bce0b7484503364c960 762 admin optional devmapper_1.02.07-1.dsc ed0ff12decdc617d9268f213ed2c1d29 923619 admin optional devmapper_1.02.07.orig.tar.gz 4a01f14aaf585cbfb8e7d2a88f03ac47 44831 admin optional devmapper_1.02.07-1.diff.gz f6776d113347ee10fb43744f88fd5f45 51844 libdevel optional libdevmapper-dev_1.02.07-1_amd64.deb b00e5a071a951a26d10f809504b2881b 41058 libs required libdevmapper1.02_1.02.07-1_amd64.deb 1cdc69ffa8c9ce18f5a9db68dca4c931 29196 debian-installer optional libdevmapper1.02-udeb_1.02.07-1_amd64.udeb 225df1b21e94d9f7694446487a5773d6 27394 admin optional
Bug#316883: marked as done (lvm2: creates device nodes as root:root 600, breaking amanda)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#341901: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: lvm2 Version: 2.01.12-2 Severity: normal Hi, unlike lvm10 (which created LV device nodes as root:disk 660), lvm2 creates its device nodes as root:root 600: brw--- 1 root root 253, 1 Jul 4 11:32 vg0-usr This precludes amanda backups from happening. Please deliver lvm2 in a way that makes the LV device nodes readable by group disk. If this can be done, please tell me how to change my local configuration to make backup possible again. Greetings Marc -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.9-zgserver Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages lvm2 depends on: ii debconf 1.4.51 Debian configuration management sy ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libdevmapper1.012:1.01.03-1 The Linux Kernel Device Mapper use ii lvm-common 1.5.19 The Logical Volume Manager for Lin lvm2 recommends no packages. -- debconf information excluded ---End Message--- ---BeginMessage--- Source: devmapper Source-Version: 2:1.02.07-1 We believe that the bug you reported is fixed in the latest version of devmapper, which is due to be installed in the Debian FTP archive: devmapper_1.02.07-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz devmapper_1.02.07-1.dsc to pool/main/d/devmapper/devmapper_1.02.07-1.dsc devmapper_1.02.07.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz dmsetup-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb dmsetup_1.02.07-1_amd64.deb to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb libdevmapper-dev_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb libdevmapper1.02-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb libdevmapper1.02_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank [EMAIL PROTECTED] (supplier of updated devmapper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 10 Jun 2006 21:20:43 + Source: devmapper Binary: dmsetup libdevmapper1.02-udeb libdevmapper1.02 libdevmapper-dev dmsetup-udeb Architecture: source amd64 Version: 2:1.02.07-1 Distribution: unstable Urgency: low Maintainer: Debian LVM Team [EMAIL PROTECTED] Changed-By: Bastian Blank [EMAIL PROTECTED] Description: dmsetup- The Linux Kernel Device Mapper userspace library dmsetup-udeb - The Linux Kernel Device Mapper userspace library (udeb) libdevmapper-dev - The Linux Kernel Device Mapper header files libdevmapper1.02 - The Linux Kernel Device Mapper userspace library libdevmapper1.02-udeb - The Linux Kernel Device Mapper userspace library (udeb) Closes: 316883 329409 341901 342455 Changes: devmapper (2:1.02.07-1) unstable; urgency=low . * New upstream version. * Update priorities to match overrides. * Acknowledge NMU. (closes: #316883, #329409, #341901, #342455) Files: 4d3f3baac4e84bce0b7484503364c960 762 admin optional devmapper_1.02.07-1.dsc ed0ff12decdc617d9268f213ed2c1d29 923619 admin optional devmapper_1.02.07.orig.tar.gz 4a01f14aaf585cbfb8e7d2a88f03ac47 44831 admin optional devmapper_1.02.07-1.diff.gz f6776d113347ee10fb43744f88fd5f45 51844 libdevel optional libdevmapper-dev_1.02.07-1_amd64.deb b00e5a071a951a26d10f809504b2881b 41058 libs required libdevmapper1.02_1.02.07-1_amd64.deb 1cdc69ffa8c9ce18f5a9db68dca4c931 29196 debian-installer optional libdevmapper1.02-udeb_1.02.07-1_amd64.udeb 225df1b21e94d9f7694446487a5773d6 27394 admin optional
Bug#342455: marked as done (tech-ctte: Ownership and permissions of device mapper block devices)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#341901: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: tech-ctte Severity: important Dear Technical Committee, Ownership and permissions of device mapper block devices This concerns Debian bugs #329409, #316883 and #341901: #329409: group and perms wrong in /dev/mapper #316883: lvm2: creates device nodes as root:root 600, breaking amanda #341901: udev: Ownership and permissions incorrect for device-mapper devices and directories The package maintainer (Bastian Blank) does not agree with the bug submitters that this is a bug, and has tagged the bugs +wontfix. He has also rejected the patches I (and others) submitted to fix this. He has agreed to my submitting this to the Technical Committee. Summary --- Disk block devices on the Debian system have historically been owned by root:disk with 0660 permissions (user and group readable and writable). This was also the case with LVM1, and also LVM2/device-mapper until earlier this year. The change was in the default device ownership and permissions of logical volume devices created under /dev/mapper by libdevmapper (in the devmapper package). This change made the LV devices different than all the other disk block devices on the Debian system. The effect of this is to break the use of the disk group. For example, the backup user is a member of the disk group, and uses the ability to read and write disk block devices in order to backup and restore backups, for example using dump/restore, tar, or a backup system such as amanda. It is not currently possible to back up or restore backups using e.g. amanda without 1) manually fixing up the ownership and permissions. This is fragile in the face of device name changes or device creation, and the changes are not preserved over a reboot, so a power cut breaks everything. I'm currently using a hacked-up init script to work around this, but it's far from perfect, and certainly not something our users should be forced to do. 2) using special udev rules, but I have yet to see any such rules in existence. The defaults are hard-coded in the devmapper package, and there is nothing the end user can do short of rebuilding the package by hand. This is simple stuff, and there is no reason it shouldn't just work if the defaults were changed back to root:disk, 0660. The discussion in #329409 and #316883 shows exactly what breaks, and both provide the same solution to the problem, which is even suggested by LVM upstream. Neither have any rationale given for the change by the maintainer. I have attached proposed patches to both bugs. #341901 is a duplicate I filed before finding the other two. Note that the udev package does not create any LVM device other than /dev/mapper; the other device creation is done purely by devmapper, and its behaviour is not configurable by an end-user. Note that this issue also affects the current stable release, sarge, so stable users cannot back up their systems. I regard this as a serious defect in the stable release, having production servers which can't be backed up without stupid hacks. If possible, I would like to get this fixed in time for the next sarge point release. Many thanks, Roger Leigh ---End Message--- ---BeginMessage--- Source: devmapper Source-Version: 2:1.02.07-1 We believe that the bug you reported is fixed in the latest version of devmapper, which is due to be installed in the Debian FTP archive: devmapper_1.02.07-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz devmapper_1.02.07-1.dsc to pool/main/d/devmapper/devmapper_1.02.07-1.dsc devmapper_1.02.07.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz dmsetup-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb dmsetup_1.02.07-1_amd64.deb to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb libdevmapper-dev_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb libdevmapper1.02-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb libdevmapper1.02_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be
Bug#341901: marked as done (udev: Ownership and permissions incorrect for device-mapper devices and directories)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#341901: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: udev Version: 0.076-3 Severity: normal The ownership and permissions for all device-mapper devices differ from other block devices on the system (root:disk, 0660): $ ls -l /dev/mapper/ total 0 crw-rw 1 root root 10, 63 2005-12-03 12:47 control brw--- 1 root root 254, 6 2005-12-03 12:48 hda_vg-cvsdata brw--- 1 root root 254, 11 2005-12-03 12:48 hda_vg-d4e82c7d--2df9--48f0--89be--ebeb500ddf2d brw--- 1 root root 254, 10 2005-12-03 12:48 hda_vg-d4e82c7d--2df9--48f0--89be--ebeb500ddf2d-cow brw--- 1 root root 254, 12 2005-12-03 12:48 hda_vg-experimental_chroot brw--- 1 root root 254, 5 2005-12-03 12:48 hda_vg-home brw--- 1 root root 254, 7 2005-12-03 12:48 hda_vg-sarge_chroot brw--- 1 root root 254, 9 2005-12-03 12:48 hda_vg-sid_chroot brw--- 1 root root 254, 8 2005-12-03 12:48 hda_vg-sid_chroot-real brw--- 1 root root 254, 0 2005-12-03 12:48 hda_vg-swap0 brw--- 1 root root 254, 1 2005-12-03 12:48 hda_vg-swap1 brw--- 1 root root 254, 2 2005-12-03 12:48 hda_vg-swap2 brw--- 1 root root 254, 3 2005-12-03 12:48 hda_vg-usr brw--- 1 root root 254, 4 2005-12-03 12:48 hda_vg-var In addition, the directories for each volume group are only readable by root: $ ls -ld /dev/hda_vg drwx-- 2 root root 260 2005-12-03 12:48 /dev/hda_vg/ The permissions on the directories should be 0775, and the owner should also be root:disk IMO. The incorrect permissions make it hard to use the disk group, e.g. for backup tools such as amanda. In short, I would very much like to 1) Have the default permissions of LVM/device-mapper devices be 0660. 2) Have the default ownership be root:disk. 3) Have the default volume group directory permissions be 0775 (including /dev/mapper). 4) Have the default volume group directory ownership be root:disk. This is also a problem for sarge, as well as unstable. If this is possible to fix by tweaking permissions.rules, that would be very handy (but for volume groups, it's not possible to know the names in advance, unlike /dev/mapper/). Thanks, Roger -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 5 lrwxrwxrwx 1 root root 20 2005-10-11 21:01 020_permissions.rules - ../permissions.rules lrwxrwxrwx 1 root root 19 2005-10-14 22:36 025_libgphoto2.rules - ../libgphoto2.rules lrwxrwxrwx 1 root root 19 2005-10-11 21:01 cd-aliases.rules - ../cd-aliases.rules -rw-r--r-- 1 root root 4957 2005-10-08 19:38 devfs.rules lrwxrwxrwx 1 root root 13 2005-10-11 21:01 udev.rules - ../udev.rules lrwxrwxrwx 1 root root 19 2005-10-11 21:01 z20_persistent.rules - ../persistent.rules lrwxrwxrwx 1 root root 12 2005-10-11 21:01 z50_run.rules - ../run.rules lrwxrwxrwx 1 root root 16 2005-10-11 21:01 z55_hotplug.rules - ../hotplug.rules lrwxrwxrwx 1 root root 19 2005-08-03 21:39 z60_alsa-utils.rules - ../alsa-utils.rules lrwxrwxrwx 1 root root 15 2005-09-20 19:13 z60_hdparm.rules - ../hdparm.rules lrwxrwxrwx 1 root root 17 2005-10-11 21:01 z70_hotplugd.rules - ../hotplugd.rules -- /sys/: /sys/block/dm-0/dev /sys/block/dm-10/dev /sys/block/dm-11/dev /sys/block/dm-12/dev /sys/block/dm-1/dev /sys/block/dm-2/dev /sys/block/dm-3/dev /sys/block/dm-4/dev /sys/block/dm-5/dev /sys/block/dm-6/dev /sys/block/dm-7/dev /sys/block/dm-8/dev /sys/block/dm-9/dev /sys/block/hda/dev /sys/block/hda/hda1/dev /sys/block/hda/hda2/dev /sys/block/hda/hda3/dev /sys/block/hda/hda4/dev /sys/block/hda/hda5/dev /sys/block/hda/hda6/dev /sys/block/hda/hda7/dev /sys/block/hdb/dev /sys/block/sda/dev /sys/block/sda/sda1/dev /sys/block/sda/sda2/dev /sys/class/adb/adb/dev /sys/class/drm/card0/dev /sys/class/graphics/fb0/dev /sys/class/i2c-dev/i2c-0/dev /sys/class/i2c-dev/i2c-1/dev /sys/class/i2c-dev/i2c-2/dev /sys/class/i2c-dev/i2c-3/dev /sys/class/i2c-dev/i2c-4/dev /sys/class/i2c-dev/i2c-5/dev /sys/class/i2c-dev/i2c-6/dev /sys/class/input/event0/dev /sys/class/input/event1/dev /sys/class/input/event2/dev /sys/class/input/event3/dev /sys/class/input/event4/dev /sys/class/input/mice/dev /sys/class/input/mouse0/dev /sys/class/input/mouse1/dev /sys/class/misc/agpgart/dev /sys/class/misc/apm_bios/dev /sys/class/misc/device-mapper/dev /sys/class/misc/nvram/dev /sys/class/misc/pmu/dev /sys/class/misc/rtc/dev /sys/class/sound/audio/dev /sys/class/sound/controlC0/dev
Bug#329409: marked as done (group and perms wrong in /dev/mapper)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#341901: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: lvm-common Version: 1.5.17 Severity: important It appears that /etc/init.d/lvm creates entries in /dev/mapper with the wrong group and permissions, which breaks various backup packages including amanda which assume they can use group disk to access the volume. The correct combination is owner root, group disk, permissions 0660. Bdale ---End Message--- ---BeginMessage--- Source: devmapper Source-Version: 2:1.02.07-1 We believe that the bug you reported is fixed in the latest version of devmapper, which is due to be installed in the Debian FTP archive: devmapper_1.02.07-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz devmapper_1.02.07-1.dsc to pool/main/d/devmapper/devmapper_1.02.07-1.dsc devmapper_1.02.07.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz dmsetup-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb dmsetup_1.02.07-1_amd64.deb to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb libdevmapper-dev_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb libdevmapper1.02-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb libdevmapper1.02_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank [EMAIL PROTECTED] (supplier of updated devmapper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 10 Jun 2006 21:20:43 + Source: devmapper Binary: dmsetup libdevmapper1.02-udeb libdevmapper1.02 libdevmapper-dev dmsetup-udeb Architecture: source amd64 Version: 2:1.02.07-1 Distribution: unstable Urgency: low Maintainer: Debian LVM Team [EMAIL PROTECTED] Changed-By: Bastian Blank [EMAIL PROTECTED] Description: dmsetup- The Linux Kernel Device Mapper userspace library dmsetup-udeb - The Linux Kernel Device Mapper userspace library (udeb) libdevmapper-dev - The Linux Kernel Device Mapper header files libdevmapper1.02 - The Linux Kernel Device Mapper userspace library libdevmapper1.02-udeb - The Linux Kernel Device Mapper userspace library (udeb) Closes: 316883 329409 341901 342455 Changes: devmapper (2:1.02.07-1) unstable; urgency=low . * New upstream version. * Update priorities to match overrides. * Acknowledge NMU. (closes: #316883, #329409, #341901, #342455) Files: 4d3f3baac4e84bce0b7484503364c960 762 admin optional devmapper_1.02.07-1.dsc ed0ff12decdc617d9268f213ed2c1d29 923619 admin optional devmapper_1.02.07.orig.tar.gz 4a01f14aaf585cbfb8e7d2a88f03ac47 44831 admin optional devmapper_1.02.07-1.diff.gz f6776d113347ee10fb43744f88fd5f45 51844 libdevel optional libdevmapper-dev_1.02.07-1_amd64.deb b00e5a071a951a26d10f809504b2881b 41058 libs required libdevmapper1.02_1.02.07-1_amd64.deb 1cdc69ffa8c9ce18f5a9db68dca4c931 29196 debian-installer optional libdevmapper1.02-udeb_1.02.07-1_amd64.udeb 225df1b21e94d9f7694446487a5773d6 27394 admin optional dmsetup_1.02.07-1_amd64.deb a861d35324f707a1ea14d6f088751242 13074 debian-installer optional dmsetup-udeb_1.02.07-1_amd64.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iEYEARECAAYFAkSLOIAACgkQLkAIIn9ODhGnGACg7ja7KFaiaKc6LsS60IHoM4OR bycAoNWw4m0c4VxK3SRZYMxQt2bCc0bz =6Bno -END PGP SIGNATURE- ---End Message---
Bug#316883: marked as done (lvm2: creates device nodes as root:root 600, breaking amanda)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#342455: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: lvm2 Version: 2.01.12-2 Severity: normal Hi, unlike lvm10 (which created LV device nodes as root:disk 660), lvm2 creates its device nodes as root:root 600: brw--- 1 root root 253, 1 Jul 4 11:32 vg0-usr This precludes amanda backups from happening. Please deliver lvm2 in a way that makes the LV device nodes readable by group disk. If this can be done, please tell me how to change my local configuration to make backup possible again. Greetings Marc -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.9-zgserver Locale: LANG=C, LC_CTYPE=de_DE (charmap=ISO-8859-1) Versions of packages lvm2 depends on: ii debconf 1.4.51 Debian configuration management sy ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libdevmapper1.012:1.01.03-1 The Linux Kernel Device Mapper use ii lvm-common 1.5.19 The Logical Volume Manager for Lin lvm2 recommends no packages. -- debconf information excluded ---End Message--- ---BeginMessage--- Source: devmapper Source-Version: 2:1.02.07-1 We believe that the bug you reported is fixed in the latest version of devmapper, which is due to be installed in the Debian FTP archive: devmapper_1.02.07-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz devmapper_1.02.07-1.dsc to pool/main/d/devmapper/devmapper_1.02.07-1.dsc devmapper_1.02.07.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz dmsetup-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb dmsetup_1.02.07-1_amd64.deb to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb libdevmapper-dev_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb libdevmapper1.02-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb libdevmapper1.02_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank [EMAIL PROTECTED] (supplier of updated devmapper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 10 Jun 2006 21:20:43 + Source: devmapper Binary: dmsetup libdevmapper1.02-udeb libdevmapper1.02 libdevmapper-dev dmsetup-udeb Architecture: source amd64 Version: 2:1.02.07-1 Distribution: unstable Urgency: low Maintainer: Debian LVM Team [EMAIL PROTECTED] Changed-By: Bastian Blank [EMAIL PROTECTED] Description: dmsetup- The Linux Kernel Device Mapper userspace library dmsetup-udeb - The Linux Kernel Device Mapper userspace library (udeb) libdevmapper-dev - The Linux Kernel Device Mapper header files libdevmapper1.02 - The Linux Kernel Device Mapper userspace library libdevmapper1.02-udeb - The Linux Kernel Device Mapper userspace library (udeb) Closes: 316883 329409 341901 342455 Changes: devmapper (2:1.02.07-1) unstable; urgency=low . * New upstream version. * Update priorities to match overrides. * Acknowledge NMU. (closes: #316883, #329409, #341901, #342455) Files: 4d3f3baac4e84bce0b7484503364c960 762 admin optional devmapper_1.02.07-1.dsc ed0ff12decdc617d9268f213ed2c1d29 923619 admin optional devmapper_1.02.07.orig.tar.gz 4a01f14aaf585cbfb8e7d2a88f03ac47 44831 admin optional devmapper_1.02.07-1.diff.gz f6776d113347ee10fb43744f88fd5f45 51844 libdevel optional libdevmapper-dev_1.02.07-1_amd64.deb b00e5a071a951a26d10f809504b2881b 41058 libs required libdevmapper1.02_1.02.07-1_amd64.deb 1cdc69ffa8c9ce18f5a9db68dca4c931 29196 debian-installer optional libdevmapper1.02-udeb_1.02.07-1_amd64.udeb 225df1b21e94d9f7694446487a5773d6 27394 admin optional
Bug#342455: marked as done (tech-ctte: Ownership and permissions of device mapper block devices)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#342455: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: tech-ctte Severity: important Dear Technical Committee, Ownership and permissions of device mapper block devices This concerns Debian bugs #329409, #316883 and #341901: #329409: group and perms wrong in /dev/mapper #316883: lvm2: creates device nodes as root:root 600, breaking amanda #341901: udev: Ownership and permissions incorrect for device-mapper devices and directories The package maintainer (Bastian Blank) does not agree with the bug submitters that this is a bug, and has tagged the bugs +wontfix. He has also rejected the patches I (and others) submitted to fix this. He has agreed to my submitting this to the Technical Committee. Summary --- Disk block devices on the Debian system have historically been owned by root:disk with 0660 permissions (user and group readable and writable). This was also the case with LVM1, and also LVM2/device-mapper until earlier this year. The change was in the default device ownership and permissions of logical volume devices created under /dev/mapper by libdevmapper (in the devmapper package). This change made the LV devices different than all the other disk block devices on the Debian system. The effect of this is to break the use of the disk group. For example, the backup user is a member of the disk group, and uses the ability to read and write disk block devices in order to backup and restore backups, for example using dump/restore, tar, or a backup system such as amanda. It is not currently possible to back up or restore backups using e.g. amanda without 1) manually fixing up the ownership and permissions. This is fragile in the face of device name changes or device creation, and the changes are not preserved over a reboot, so a power cut breaks everything. I'm currently using a hacked-up init script to work around this, but it's far from perfect, and certainly not something our users should be forced to do. 2) using special udev rules, but I have yet to see any such rules in existence. The defaults are hard-coded in the devmapper package, and there is nothing the end user can do short of rebuilding the package by hand. This is simple stuff, and there is no reason it shouldn't just work if the defaults were changed back to root:disk, 0660. The discussion in #329409 and #316883 shows exactly what breaks, and both provide the same solution to the problem, which is even suggested by LVM upstream. Neither have any rationale given for the change by the maintainer. I have attached proposed patches to both bugs. #341901 is a duplicate I filed before finding the other two. Note that the udev package does not create any LVM device other than /dev/mapper; the other device creation is done purely by devmapper, and its behaviour is not configurable by an end-user. Note that this issue also affects the current stable release, sarge, so stable users cannot back up their systems. I regard this as a serious defect in the stable release, having production servers which can't be backed up without stupid hacks. If possible, I would like to get this fixed in time for the next sarge point release. Many thanks, Roger Leigh ---End Message--- ---BeginMessage--- Source: devmapper Source-Version: 2:1.02.07-1 We believe that the bug you reported is fixed in the latest version of devmapper, which is due to be installed in the Debian FTP archive: devmapper_1.02.07-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz devmapper_1.02.07-1.dsc to pool/main/d/devmapper/devmapper_1.02.07-1.dsc devmapper_1.02.07.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz dmsetup-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb dmsetup_1.02.07-1_amd64.deb to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb libdevmapper-dev_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb libdevmapper1.02-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb libdevmapper1.02_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be
Bug#329409: marked as done (group and perms wrong in /dev/mapper)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#342455: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: lvm-common Version: 1.5.17 Severity: important It appears that /etc/init.d/lvm creates entries in /dev/mapper with the wrong group and permissions, which breaks various backup packages including amanda which assume they can use group disk to access the volume. The correct combination is owner root, group disk, permissions 0660. Bdale ---End Message--- ---BeginMessage--- Source: devmapper Source-Version: 2:1.02.07-1 We believe that the bug you reported is fixed in the latest version of devmapper, which is due to be installed in the Debian FTP archive: devmapper_1.02.07-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz devmapper_1.02.07-1.dsc to pool/main/d/devmapper/devmapper_1.02.07-1.dsc devmapper_1.02.07.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz dmsetup-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb dmsetup_1.02.07-1_amd64.deb to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb libdevmapper-dev_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb libdevmapper1.02-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb libdevmapper1.02_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank [EMAIL PROTECTED] (supplier of updated devmapper package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Sat, 10 Jun 2006 21:20:43 + Source: devmapper Binary: dmsetup libdevmapper1.02-udeb libdevmapper1.02 libdevmapper-dev dmsetup-udeb Architecture: source amd64 Version: 2:1.02.07-1 Distribution: unstable Urgency: low Maintainer: Debian LVM Team [EMAIL PROTECTED] Changed-By: Bastian Blank [EMAIL PROTECTED] Description: dmsetup- The Linux Kernel Device Mapper userspace library dmsetup-udeb - The Linux Kernel Device Mapper userspace library (udeb) libdevmapper-dev - The Linux Kernel Device Mapper header files libdevmapper1.02 - The Linux Kernel Device Mapper userspace library libdevmapper1.02-udeb - The Linux Kernel Device Mapper userspace library (udeb) Closes: 316883 329409 341901 342455 Changes: devmapper (2:1.02.07-1) unstable; urgency=low . * New upstream version. * Update priorities to match overrides. * Acknowledge NMU. (closes: #316883, #329409, #341901, #342455) Files: 4d3f3baac4e84bce0b7484503364c960 762 admin optional devmapper_1.02.07-1.dsc ed0ff12decdc617d9268f213ed2c1d29 923619 admin optional devmapper_1.02.07.orig.tar.gz 4a01f14aaf585cbfb8e7d2a88f03ac47 44831 admin optional devmapper_1.02.07-1.diff.gz f6776d113347ee10fb43744f88fd5f45 51844 libdevel optional libdevmapper-dev_1.02.07-1_amd64.deb b00e5a071a951a26d10f809504b2881b 41058 libs required libdevmapper1.02_1.02.07-1_amd64.deb 1cdc69ffa8c9ce18f5a9db68dca4c931 29196 debian-installer optional libdevmapper1.02-udeb_1.02.07-1_amd64.udeb 225df1b21e94d9f7694446487a5773d6 27394 admin optional dmsetup_1.02.07-1_amd64.deb a861d35324f707a1ea14d6f088751242 13074 debian-installer optional dmsetup-udeb_1.02.07-1_amd64.udeb Package-Type: udeb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iEYEARECAAYFAkSLOIAACgkQLkAIIn9ODhGnGACg7ja7KFaiaKc6LsS60IHoM4OR bycAoNWw4m0c4VxK3SRZYMxQt2bCc0bz =6Bno -END PGP SIGNATURE- ---End Message---
Bug#341901: marked as done (udev: Ownership and permissions incorrect for device-mapper devices and directories)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#342455: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: udev Version: 0.076-3 Severity: normal The ownership and permissions for all device-mapper devices differ from other block devices on the system (root:disk, 0660): $ ls -l /dev/mapper/ total 0 crw-rw 1 root root 10, 63 2005-12-03 12:47 control brw--- 1 root root 254, 6 2005-12-03 12:48 hda_vg-cvsdata brw--- 1 root root 254, 11 2005-12-03 12:48 hda_vg-d4e82c7d--2df9--48f0--89be--ebeb500ddf2d brw--- 1 root root 254, 10 2005-12-03 12:48 hda_vg-d4e82c7d--2df9--48f0--89be--ebeb500ddf2d-cow brw--- 1 root root 254, 12 2005-12-03 12:48 hda_vg-experimental_chroot brw--- 1 root root 254, 5 2005-12-03 12:48 hda_vg-home brw--- 1 root root 254, 7 2005-12-03 12:48 hda_vg-sarge_chroot brw--- 1 root root 254, 9 2005-12-03 12:48 hda_vg-sid_chroot brw--- 1 root root 254, 8 2005-12-03 12:48 hda_vg-sid_chroot-real brw--- 1 root root 254, 0 2005-12-03 12:48 hda_vg-swap0 brw--- 1 root root 254, 1 2005-12-03 12:48 hda_vg-swap1 brw--- 1 root root 254, 2 2005-12-03 12:48 hda_vg-swap2 brw--- 1 root root 254, 3 2005-12-03 12:48 hda_vg-usr brw--- 1 root root 254, 4 2005-12-03 12:48 hda_vg-var In addition, the directories for each volume group are only readable by root: $ ls -ld /dev/hda_vg drwx-- 2 root root 260 2005-12-03 12:48 /dev/hda_vg/ The permissions on the directories should be 0775, and the owner should also be root:disk IMO. The incorrect permissions make it hard to use the disk group, e.g. for backup tools such as amanda. In short, I would very much like to 1) Have the default permissions of LVM/device-mapper devices be 0660. 2) Have the default ownership be root:disk. 3) Have the default volume group directory permissions be 0775 (including /dev/mapper). 4) Have the default volume group directory ownership be root:disk. This is also a problem for sarge, as well as unstable. If this is possible to fix by tweaking permissions.rules, that would be very handy (but for volume groups, it's not possible to know the names in advance, unlike /dev/mapper/). Thanks, Roger -- Package-specific info: -- /etc/udev/rules.d/: /etc/udev/rules.d/: total 5 lrwxrwxrwx 1 root root 20 2005-10-11 21:01 020_permissions.rules - ../permissions.rules lrwxrwxrwx 1 root root 19 2005-10-14 22:36 025_libgphoto2.rules - ../libgphoto2.rules lrwxrwxrwx 1 root root 19 2005-10-11 21:01 cd-aliases.rules - ../cd-aliases.rules -rw-r--r-- 1 root root 4957 2005-10-08 19:38 devfs.rules lrwxrwxrwx 1 root root 13 2005-10-11 21:01 udev.rules - ../udev.rules lrwxrwxrwx 1 root root 19 2005-10-11 21:01 z20_persistent.rules - ../persistent.rules lrwxrwxrwx 1 root root 12 2005-10-11 21:01 z50_run.rules - ../run.rules lrwxrwxrwx 1 root root 16 2005-10-11 21:01 z55_hotplug.rules - ../hotplug.rules lrwxrwxrwx 1 root root 19 2005-08-03 21:39 z60_alsa-utils.rules - ../alsa-utils.rules lrwxrwxrwx 1 root root 15 2005-09-20 19:13 z60_hdparm.rules - ../hdparm.rules lrwxrwxrwx 1 root root 17 2005-10-11 21:01 z70_hotplugd.rules - ../hotplugd.rules -- /sys/: /sys/block/dm-0/dev /sys/block/dm-10/dev /sys/block/dm-11/dev /sys/block/dm-12/dev /sys/block/dm-1/dev /sys/block/dm-2/dev /sys/block/dm-3/dev /sys/block/dm-4/dev /sys/block/dm-5/dev /sys/block/dm-6/dev /sys/block/dm-7/dev /sys/block/dm-8/dev /sys/block/dm-9/dev /sys/block/hda/dev /sys/block/hda/hda1/dev /sys/block/hda/hda2/dev /sys/block/hda/hda3/dev /sys/block/hda/hda4/dev /sys/block/hda/hda5/dev /sys/block/hda/hda6/dev /sys/block/hda/hda7/dev /sys/block/hdb/dev /sys/block/sda/dev /sys/block/sda/sda1/dev /sys/block/sda/sda2/dev /sys/class/adb/adb/dev /sys/class/drm/card0/dev /sys/class/graphics/fb0/dev /sys/class/i2c-dev/i2c-0/dev /sys/class/i2c-dev/i2c-1/dev /sys/class/i2c-dev/i2c-2/dev /sys/class/i2c-dev/i2c-3/dev /sys/class/i2c-dev/i2c-4/dev /sys/class/i2c-dev/i2c-5/dev /sys/class/i2c-dev/i2c-6/dev /sys/class/input/event0/dev /sys/class/input/event1/dev /sys/class/input/event2/dev /sys/class/input/event3/dev /sys/class/input/event4/dev /sys/class/input/mice/dev /sys/class/input/mouse0/dev /sys/class/input/mouse1/dev /sys/class/misc/agpgart/dev /sys/class/misc/apm_bios/dev /sys/class/misc/device-mapper/dev /sys/class/misc/nvram/dev /sys/class/misc/pmu/dev /sys/class/misc/rtc/dev /sys/class/sound/audio/dev /sys/class/sound/controlC0/dev
Bug#342455: marked as done (tech-ctte: Ownership and permissions of device mapper block devices)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#316883: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: tech-ctte Severity: important Dear Technical Committee, Ownership and permissions of device mapper block devices This concerns Debian bugs #329409, #316883 and #341901: #329409: group and perms wrong in /dev/mapper #316883: lvm2: creates device nodes as root:root 600, breaking amanda #341901: udev: Ownership and permissions incorrect for device-mapper devices and directories The package maintainer (Bastian Blank) does not agree with the bug submitters that this is a bug, and has tagged the bugs +wontfix. He has also rejected the patches I (and others) submitted to fix this. He has agreed to my submitting this to the Technical Committee. Summary --- Disk block devices on the Debian system have historically been owned by root:disk with 0660 permissions (user and group readable and writable). This was also the case with LVM1, and also LVM2/device-mapper until earlier this year. The change was in the default device ownership and permissions of logical volume devices created under /dev/mapper by libdevmapper (in the devmapper package). This change made the LV devices different than all the other disk block devices on the Debian system. The effect of this is to break the use of the disk group. For example, the backup user is a member of the disk group, and uses the ability to read and write disk block devices in order to backup and restore backups, for example using dump/restore, tar, or a backup system such as amanda. It is not currently possible to back up or restore backups using e.g. amanda without 1) manually fixing up the ownership and permissions. This is fragile in the face of device name changes or device creation, and the changes are not preserved over a reboot, so a power cut breaks everything. I'm currently using a hacked-up init script to work around this, but it's far from perfect, and certainly not something our users should be forced to do. 2) using special udev rules, but I have yet to see any such rules in existence. The defaults are hard-coded in the devmapper package, and there is nothing the end user can do short of rebuilding the package by hand. This is simple stuff, and there is no reason it shouldn't just work if the defaults were changed back to root:disk, 0660. The discussion in #329409 and #316883 shows exactly what breaks, and both provide the same solution to the problem, which is even suggested by LVM upstream. Neither have any rationale given for the change by the maintainer. I have attached proposed patches to both bugs. #341901 is a duplicate I filed before finding the other two. Note that the udev package does not create any LVM device other than /dev/mapper; the other device creation is done purely by devmapper, and its behaviour is not configurable by an end-user. Note that this issue also affects the current stable release, sarge, so stable users cannot back up their systems. I regard this as a serious defect in the stable release, having production servers which can't be backed up without stupid hacks. If possible, I would like to get this fixed in time for the next sarge point release. Many thanks, Roger Leigh ---End Message--- ---BeginMessage--- Source: devmapper Source-Version: 2:1.02.07-1 We believe that the bug you reported is fixed in the latest version of devmapper, which is due to be installed in the Debian FTP archive: devmapper_1.02.07-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz devmapper_1.02.07-1.dsc to pool/main/d/devmapper/devmapper_1.02.07-1.dsc devmapper_1.02.07.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz dmsetup-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb dmsetup_1.02.07-1_amd64.deb to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb libdevmapper-dev_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb libdevmapper1.02-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb libdevmapper1.02_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be
Bug#342455: marked as done (tech-ctte: Ownership and permissions of device mapper block devices)
Your message dated Sat, 10 Jun 2006 14:47:10 -0700 with message-id [EMAIL PROTECTED] and subject line Bug#329409: fixed in devmapper 2:1.02.07-1 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: tech-ctte Severity: important Dear Technical Committee, Ownership and permissions of device mapper block devices This concerns Debian bugs #329409, #316883 and #341901: #329409: group and perms wrong in /dev/mapper #316883: lvm2: creates device nodes as root:root 600, breaking amanda #341901: udev: Ownership and permissions incorrect for device-mapper devices and directories The package maintainer (Bastian Blank) does not agree with the bug submitters that this is a bug, and has tagged the bugs +wontfix. He has also rejected the patches I (and others) submitted to fix this. He has agreed to my submitting this to the Technical Committee. Summary --- Disk block devices on the Debian system have historically been owned by root:disk with 0660 permissions (user and group readable and writable). This was also the case with LVM1, and also LVM2/device-mapper until earlier this year. The change was in the default device ownership and permissions of logical volume devices created under /dev/mapper by libdevmapper (in the devmapper package). This change made the LV devices different than all the other disk block devices on the Debian system. The effect of this is to break the use of the disk group. For example, the backup user is a member of the disk group, and uses the ability to read and write disk block devices in order to backup and restore backups, for example using dump/restore, tar, or a backup system such as amanda. It is not currently possible to back up or restore backups using e.g. amanda without 1) manually fixing up the ownership and permissions. This is fragile in the face of device name changes or device creation, and the changes are not preserved over a reboot, so a power cut breaks everything. I'm currently using a hacked-up init script to work around this, but it's far from perfect, and certainly not something our users should be forced to do. 2) using special udev rules, but I have yet to see any such rules in existence. The defaults are hard-coded in the devmapper package, and there is nothing the end user can do short of rebuilding the package by hand. This is simple stuff, and there is no reason it shouldn't just work if the defaults were changed back to root:disk, 0660. The discussion in #329409 and #316883 shows exactly what breaks, and both provide the same solution to the problem, which is even suggested by LVM upstream. Neither have any rationale given for the change by the maintainer. I have attached proposed patches to both bugs. #341901 is a duplicate I filed before finding the other two. Note that the udev package does not create any LVM device other than /dev/mapper; the other device creation is done purely by devmapper, and its behaviour is not configurable by an end-user. Note that this issue also affects the current stable release, sarge, so stable users cannot back up their systems. I regard this as a serious defect in the stable release, having production servers which can't be backed up without stupid hacks. If possible, I would like to get this fixed in time for the next sarge point release. Many thanks, Roger Leigh ---End Message--- ---BeginMessage--- Source: devmapper Source-Version: 2:1.02.07-1 We believe that the bug you reported is fixed in the latest version of devmapper, which is due to be installed in the Debian FTP archive: devmapper_1.02.07-1.diff.gz to pool/main/d/devmapper/devmapper_1.02.07-1.diff.gz devmapper_1.02.07-1.dsc to pool/main/d/devmapper/devmapper_1.02.07-1.dsc devmapper_1.02.07.orig.tar.gz to pool/main/d/devmapper/devmapper_1.02.07.orig.tar.gz dmsetup-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/dmsetup-udeb_1.02.07-1_amd64.udeb dmsetup_1.02.07-1_amd64.deb to pool/main/d/devmapper/dmsetup_1.02.07-1_amd64.deb libdevmapper-dev_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper-dev_1.02.07-1_amd64.deb libdevmapper1.02-udeb_1.02.07-1_amd64.udeb to pool/main/d/devmapper/libdevmapper1.02-udeb_1.02.07-1_amd64.udeb libdevmapper1.02_1.02.07-1_amd64.deb to pool/main/d/devmapper/libdevmapper1.02_1.02.07-1_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be
