Bug#435983: mount: fails to detect LABEL=foo filesystems
also sprach Marco d'Itri [EMAIL PROTECTED] [2007.08.11.1829 +0200]: Can someone please explain what changed (package/version) that this is causing problems? mount dropped its own code to parse LABEL= and UUID= and now uses the persistent names created by udev. The lvm and mdadm packages need to ship a rules file to create them. I will try to post them tomorrow. Do you know if the Ubuntu package's udev integration does what we want? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#435983: mount: fails to detect LABEL=foo filesystems
Marco d'Itri wrote: On Mar 14, Holger Levsen [EMAIL PROTECTED] wrote: also sprach Marco d'Itri [EMAIL PROTECTED] [2007.09.10.1409 +0200]: I will do it ASAP. Please do not do this by yourself because the udev rules files need to be renamed first (or else I would need to add conflicts and you would need to move the file). Marco, any news on this? Yes, I still hold the same opinion and still plan to work on udev ASAP. Do not add these rules without my approval. This bug is causing trouble for more and more people. Please, Marco, if you do not have the time to fix it by adding these rules, at least let us know what are the changes you though to at least let anyone else work on them, even if you are the one approving them. Ahora también puedes acceder a tu correo Terra desde el móvil. Infórmate pinchando aquí. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
also sprach Marco d'Itri [EMAIL PROTECTED] [2007.09.10.1409 +0200]: I will do it ASAP. Please do not do this by yourself because the udev rules files need to be renamed first (or else I would need to add conflicts and you would need to move the file). Can you please give me an ETA? Tomorrow? Two weeks? End of October? Anything is fine with me, really, I just want to be able to plan. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems the only way to get rid of a temptation is to yield to it. -- oscar wilde digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#435983: mount: fails to detect LABEL=foo filesystems
On Sep 06, martin f krafft [EMAIL PROTECTED] wrote: I am going to prepare a new mdadm package soon and it would be nice if you could send me the udev rules file for that (and maybe some instructions as to what else I have to do). I will do it ASAP. Please do not do this by yourself because the udev rules files need to be renamed first (or else I would need to add conflicts and you would need to move the file). -- ciao, Marco signature.asc Description: Digital signature
Bug#435983: mount: fails to detect LABEL=foo filesystems
tags 435983 help moreinfo retitle 435983 please add udev rules to make mdadm register /dev/disk symlinks thanks also sprach Marco d'Itri [EMAIL PROTECTED] [2007.08.11.1829 +0200]: mount dropped its own code to parse LABEL= and UUID= and now uses the persistent names created by udev. The lvm and mdadm packages need to ship a rules file to create them. I will try to post them tomorrow. Hi Marco, I am going to prepare a new mdadm package soon and it would be nice if you could send me the udev rules file for that (and maybe some instructions as to what else I have to do). Cheers, -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Bug#435983: mount: fails to detect LABEL=foo filesystems
On Thu, Aug 09, 2007 at 11:06:34AM +0200, Marco d'Itri wrote: On Aug 09, James Youngman [EMAIL PROTECTED] wrote: OK. But FWIW I would have appreciated some advance warning that the configuration I was using [*] was deprecated and support would be withdrawn soon, before the support was actually withdrawn. It's not deprecated, LVM and mdadm needs to be fixed to support it. Can someone please explain what changed (package/version) that this is causing problems? Is this a problem for etch, or just lenny/sid? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
On Aug 11, Kurt Roeckx [EMAIL PROTECTED] wrote: Can someone please explain what changed (package/version) that this is causing problems? mount dropped its own code to parse LABEL= and UUID= and now uses the persistent names created by udev. The lvm and mdadm packages need to ship a rules file to create them. I will try to post them tomorrow. Is this a problem for etch, or just lenny/sid? Just sid. -- ciao, Marco signature.asc Description: Digital signature
Bug#435983: mount: fails to detect LABEL=foo filesystems
On 8/7/07, Touko Korpela [EMAIL PROTECTED] wrote: Please tell udev version installed. ~$ dpkg -l udev Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii udev 0.114-2/dev/ and hotplug management daemon $ debconf-show udev debconf: DbDriver passwords warning: could not open /var/cache/debconf/passwords.dat: Permission denied udev/new_kernel_needed: false udev/reboot_needed: $ dpkg --status udev Package: udev Status: install ok installed Priority: important Section: admin Installed-Size: 940 Maintainer: Marco d'Itri [EMAIL PROTECTED] Architecture: i386 Version: 0.114-2 Replaces: initramfs-tools (= 0.41) Depends: libc6 (= 2.6-1), libselinux1 (= 2.0.15), libvolume-id0 (= 0.113), debconf (= 0.5) | debconf-2.0, lsb-base (= 3.0-6) Pre-Depends: debconf (= 1.4.69) | debconf-2.0 Conflicts: hotplug, initscripts ( 2.85-16), lvm-common ( 1.5.13), module-init-tools ( 3.2.2-1), initramfs-tools ( 0.39), hal ( 0.5.6-2), makedev ( 2.3.1-80), klibc-utils (= 1.4.19-1), multipath-tools ( 0.4.7-2) Conffiles: /etc/modprobe.d/pnp-hotplug 57e7aba8b91e5a19028a0303065a1901 /etc/modprobe.d/display_class 34eba9ad8e27d458fc5efbaa3a88f2a5 /etc/modprobe.d/blacklist c8770183ed0c9f92b7a7d7fba17a82df /etc/init.d/udev 55c8d6f187f340aba0f4b85425f48f02 /etc/init.d/udev-mtab 82a581c2e19b357c35c83124dd0caaa3 /etc/udev/udev.conf 3f1d43d19e4e26fc4f87bbaa542ff12a /etc/udev/run.rules a5625f4c4c541beb546206ee0e5e277f /etc/udev/links.conf 50f175cab5d8c503598a157b6e485e1b /etc/udev/compat-full.rules 659b834be979c31d82f9acdf93ea9a66 /etc/udev/persistent-input.rules cc058acc1f41fa6b42aad44879c0ff81 /etc/udev/persistent.rules a165cf8371ee03c9ceb79a79f62b6997 /etc/udev/cd-aliases-generator.rules 3a3dbd5c53c4f1483584f9b4a1a94e11 /etc/udev/udev.rules ae413acf9642c9b537ca7cd4bee0bd71 /etc/udev/devfs.rules 7e073717976a9e23dc802ec14a6be823 /etc/udev/hotplug.rules 9adb481d6122dc08527f630a9d2ec753 /etc/udev/permissions.rules b3cbbeac6047decccda7acec7d2c64ed /etc/udev/persistent-net-generator.rules b629bc89c46df58da0d75858081bb74b /etc/udev/compat.rules 465b423d2d5b52ee2be30e16dfbe4cfb /etc/scsi_id.config 90c176456f98d5f9407cc8a7540ae1d8 Description: /dev/ and hotplug management daemon udev is a daemon which dynamically creates and removes device nodes from /dev/, handles hotplug events and loads drivers at boot time. It replaces the hotplug package and requires a 2.6.15 or newer kernel version. You are using 2.6.18-4-xen-686 kernel from etch? Is xen in use? Aha. Until you mentioned this, I had not recalled that the 2.6.15 kernel I was running was in fact a self-built kernel. I normally don't boot the Xen kernel, I normally use the 2.6.15 kernel, but I had not remembered that that's also a custom kernel. $ dpkg -l linux-image-2.6.15 linux-xen0-2.6.18-4-xen-686 Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii linux-image-2.6.15 jy.1.0 Linux kernel binary image for version 2.6.15 ii linux-xen0-2.6.18-4-xe Custom.1 Linux xen kernel binary image for version 2.6.18-4-xen-686 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
On 8/8/07, Marco d'Itri [EMAIL PROTECTED] wrote: On Aug 04, James Youngman [EMAIL PROTECTED] wrote: LABEL=foo entries can no longer be mounted; I love generalizations... So, whatever populates /dev/disk/by-label is not aware of (LVM2 MD), This is the real problem. The mdadm maintainer needs to integrate in his package support for persistent device names (i.e. install the appropriate rules file). Really? But the missing entries in /dev/disk/by-label are the LVM logical volumes, not the MD devices.I don't directly mount any of the MD devices. James. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
On Aug 09, James Youngman [EMAIL PROTECTED] wrote: So, whatever populates /dev/disk/by-label is not aware of (LVM2 MD), This is the real problem. The mdadm maintainer needs to integrate in his package support for persistent device names (i.e. install the appropriate rules file). Really? But the missing entries in /dev/disk/by-label are the LVM logical volumes, not the MD devices.I don't directly mount any of the MD devices. Really. But if your problems are caused by LVM devices then you should talk with the LVM maintainers too. -- ciao, Marco signature.asc Description: Digital signature
Bug#435983: mount: fails to detect LABEL=foo filesystems
On 8/9/07, Marco d'Itri [EMAIL PROTECTED] wrote: Really. But if your problems are caused by LVM devices then you should talk with the LVM maintainers too. OK. But FWIW I would have appreciated some advance warning that the configuration I was using [*] was deprecated and support would be withdrawn soon, before the support was actually withdrawn. [*] The configuration I'm using which is not supported is having filesystems mounted via LABEL= in /etc/fstab where the corresponding entry does not exist in /dev/disk/by-label/. Thanks, James. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
On Aug 09, James Youngman [EMAIL PROTECTED] wrote: OK. But FWIW I would have appreciated some advance warning that the configuration I was using [*] was deprecated and support would be withdrawn soon, before the support was actually withdrawn. It's not deprecated, LVM and mdadm needs to be fixed to support it. -- ciao, Marco signature.asc Description: Digital signature
Bug#435983: mount: fails to detect LABEL=foo filesystems
On Aug 04, James Youngman [EMAIL PROTECTED] wrote: LABEL=foo entries can no longer be mounted; I love generalizations... So, whatever populates /dev/disk/by-label is not aware of (LVM2 MD), This is the real problem. The mdadm maintainer needs to integrate in his package support for persistent device names (i.e. install the appropriate rules file). -- ciao, Marco signature.asc Description: Digital signature
Bug#435983: mount: fails to detect LABEL=foo filesystems
reassign 435983 mdadm -- done On Wed, Aug 08, 2007 at 03:44:32PM +0200, Marco d'Itri wrote: On Aug 04, James Youngman [EMAIL PROTECTED] wrote: LABEL=foo entries can no longer be mounted; I love generalizations... So, whatever populates /dev/disk/by-label is not aware of (LVM2 MD), This is the real problem. The mdadm maintainer needs to integrate in his package support for persistent device names (i.e. install the appropriate rules file). -- ciao, Marco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
Please tell udev version installed. You are using 2.6.18-4-xen-686 kernel from etch? Is xen in use? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
On Sat, Aug 04, 2007 at 02:43:04PM +0100, James Youngman wrote: Everything worked fine 'til I upgraded... So, whatever populates /dev/disk/by-label is not aware of (LVM2 MD), and since mount no longer itself supports LABEL= directly, mount fails to mopunt perfectly good filesystems. This makes the system unusable. The latest mdadm package seems to provide hooks for vol_id to populate /dev/disk/*. I expect that the latest LVM does as well.. In any case, it would appear to be a bug in udev or lvm for not populating the table that libvolume-id is using. Does the lvm2 package in sid fix the issue? lamont -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
On 8/5/07, LaMont Jones [EMAIL PROTECTED] wrote: On Sat, Aug 04, 2007 at 02:43:04PM +0100, James Youngman wrote: Everything worked fine 'til I upgraded... So, whatever populates /dev/disk/by-label is not aware of (LVM2 MD), and since mount no longer itself supports LABEL= directly, mount fails to mopunt perfectly good filesystems. This makes the system unusable. The latest mdadm package seems to provide hooks for vol_id to populate /dev/disk/*. I expect that the latest LVM does as well.. In any case, it would appear to be a bug in udev or lvm for not populating the table that libvolume-id is using. Does the lvm2 package in sid fix the issue? I upgraded to that just now in order to answer your question. It does not fix the issue. ii lvm2 2.02.26-1+b1 The Linux Logical Volume Manager FWIW, fsck still works fine in this configuration; the filesystems can be checked but not mounted. IMO, if we're going to withdraw a feature that people are depending on in order to boot (and I have been depending on it for the past four years), we should really provide people with a warning and some time window in which to change their configuration. James. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#435983: mount: fails to detect LABEL=foo filesystems
Package: mount Version: 2.13~rc2-5 Severity: critical Justification: breaks the whole system Everything worked fine 'til I upgraded... LABEL=foo entries can no longer be mounted; this causes the system to be wholly unusable if (say) /usr is mounted via a labelled filesystem. I've been using LABEL=foo on Debian systems since about 2003, and this is the first time I've had a problem with doing it. My fstab file looks like this:- # /etc/fstab: static file system information. LABEL=usr-src /usr/srcext3defaults0 6 LABEL=backups /backupsext3defaults,ro 0 9 LABEL=/export /export ext3defaults,ro 0 10 If I try to mout a filesystem, I get this result:- # mount /usr/src mount: special device /dev/disk/by-label/usr-src does not exist There are entries in /dev/disk/by-label for devices on /def/hda[0-9], but most of my filesystems are on LVM2 volumes (and the physical volumes are either RAID0 or RAID1 volumed managed by MD). So, whatever populates /dev/disk/by-label is not aware of (LVM2 MD), and since mount no longer itself supports LABEL= directly, mount fails to mopunt perfectly good filesystems. This makes the system unusable. Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription ii lvm2 2.02.06-4 The Linux Logical Volume Manager -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-xen-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.ISO-8859-15, LC_CTYPE=en_GB.ISO-8859-15 (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages mount depends on: ii libc62.6-5 GNU C Library: Shared libraries ii libselinux1 2.0.15-2+b1 SELinux shared libraries ii libvolume-id00.113-3 libvolume_id shared library Versions of packages mount recommends: ii nfs-common1:1.1.0-13 NFS support files common to client -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
