* film at 11: kernel update breaks udev. @ 2007-07-21 1:04 Dave Jones 2007-07-21 1:09 ` Kay Sievers 0 siblings, 1 reply; 7+ messages in thread From: Dave Jones @ 2007-07-21 1:04 UTC (permalink / raw) To: Linux Kernel Just one of my machines to 2.6.22.1, and got this during boot.. Starting udev: udevd-event[619]: udev_node_symlink: symlink(../../sdc/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89) failed: File exists Under 2.6.21, all was fine. sdc is one disk of a 3 disk raid5 set. The raidset still manages to come up despite this. This is a Fedora 7 box, with udev-106-4.1.fc7 What changed this time? Dave -- http://www.codemonkey.org.uk ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: film at 11: kernel update breaks udev. 2007-07-21 1:04 film at 11: kernel update breaks udev Dave Jones @ 2007-07-21 1:09 ` Kay Sievers 2007-07-21 1:16 ` Dave Jones 0 siblings, 1 reply; 7+ messages in thread From: Kay Sievers @ 2007-07-21 1:09 UTC (permalink / raw) To: Dave Jones, Linux Kernel On 7/21/07, Dave Jones <davej@redhat.com> wrote: > Just one of my machines to 2.6.22.1, and got this during boot.. > > Starting udev: udevd-event[619]: udev_node_symlink: symlink(../../sdc/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89) failed: File exists > > Under 2.6.21, all was fine. > > sdc is one disk of a 3 disk raid5 set. > The raidset still manages to come up despite this. > > This is a Fedora 7 box, with udev-106-4.1.fc7 > > What changed this time? CONFIG_BLK_DEV_BSG=y? There's a name-clash, because bsg tries to create devices with the same name. James sent a patch, it's on lkml. Kay ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: film at 11: kernel update breaks udev. 2007-07-21 1:09 ` Kay Sievers @ 2007-07-21 1:16 ` Dave Jones 2007-07-21 1:28 ` Kay Sievers 0 siblings, 1 reply; 7+ messages in thread From: Dave Jones @ 2007-07-21 1:16 UTC (permalink / raw) To: Kay Sievers; +Cc: Linux Kernel On Sat, Jul 21, 2007 at 03:09:55AM +0200, Kay Sievers wrote: > On 7/21/07, Dave Jones <davej@redhat.com> wrote: > > Just one of my machines to 2.6.22.1, and got this during boot.. > > > > Starting udev: udevd-event[619]: udev_node_symlink: symlink(../../sdc/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89) failed: File exists > > > > Under 2.6.21, all was fine. > > > > sdc is one disk of a 3 disk raid5 set. > > The raidset still manages to come up despite this. > > > > This is a Fedora 7 box, with udev-106-4.1.fc7 > > > > What changed this time? > > CONFIG_BLK_DEV_BSG=y? > > There's a name-clash, because bsg tries to create devices with the same name. > James sent a patch, it's on lkml. BSG isn't in 2.6.22 Dave -- http://www.codemonkey.org.uk ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: film at 11: kernel update breaks udev. 2007-07-21 1:16 ` Dave Jones @ 2007-07-21 1:28 ` Kay Sievers 2007-07-21 1:36 ` Dave Jones 0 siblings, 1 reply; 7+ messages in thread From: Kay Sievers @ 2007-07-21 1:28 UTC (permalink / raw) To: Dave Jones, Kay Sievers, Linux Kernel On 7/21/07, Dave Jones <davej@redhat.com> wrote: > On Sat, Jul 21, 2007 at 03:09:55AM +0200, Kay Sievers wrote: > > On 7/21/07, Dave Jones <davej@redhat.com> wrote: > > > Just one of my machines to 2.6.22.1, and got this during boot.. > > > > > > Starting udev: udevd-event[619]: udev_node_symlink: symlink(../../sdc/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89) failed: File exists > > > > > > Under 2.6.21, all was fine. > > > > > > sdc is one disk of a 3 disk raid5 set. > > > The raidset still manages to come up despite this. > > > > > > This is a Fedora 7 box, with udev-106-4.1.fc7 > > > > > > What changed this time? > > > > CONFIG_BLK_DEV_BSG=y? > > > > There's a name-clash, because bsg tries to create devices with the same name. > > James sent a patch, it's on lkml. > > BSG isn't in 2.6.22 Ok. There has nothing else changed, that I could think of what could cause this. The code in udev that prints this message looks like: err("symlink(%s, %s) failed: %s", linktarget, filename, strerror(errno)); That doesn't really match what you posted. Are there chars missing? Can you please recheck? And what does: udevtest /block/sdc print? Thanks, Kay ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: film at 11: kernel update breaks udev. 2007-07-21 1:28 ` Kay Sievers @ 2007-07-21 1:36 ` Dave Jones 2007-07-21 1:55 ` Kay Sievers 0 siblings, 1 reply; 7+ messages in thread From: Dave Jones @ 2007-07-21 1:36 UTC (permalink / raw) To: Kay Sievers; +Cc: Linux Kernel On Sat, Jul 21, 2007 at 03:28:12AM +0200, Kay Sievers wrote: > On 7/21/07, Dave Jones <davej@redhat.com> wrote: > > On Sat, Jul 21, 2007 at 03:09:55AM +0200, Kay Sievers wrote: > > > On 7/21/07, Dave Jones <davej@redhat.com> wrote: > > > > Just one of my machines to 2.6.22.1, and got this during boot.. > > > > > > > > Starting udev: udevd-event[619]: udev_node_symlink: symlink(../../sdc/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89) failed: File exists > > > > > > > > Under 2.6.21, all was fine. > > > > > > > > sdc is one disk of a 3 disk raid5 set. > > > > The raidset still manages to come up despite this. > > > > > > > > This is a Fedora 7 box, with udev-106-4.1.fc7 > > > > > > > > What changed this time? > > > > > > CONFIG_BLK_DEV_BSG=y? > > > > > > There's a name-clash, because bsg tries to create devices with the same name. > > > James sent a patch, it's on lkml. > > > > BSG isn't in 2.6.22 > > Ok. There has nothing else changed, that I could think of what could cause this. > > The code in udev that prints this message looks like: > err("symlink(%s, %s) failed: %s", linktarget, filename, strerror(errno)); > > That doesn't really match what you posted. Are there chars missing? Umm. Now I'm confused. Note above that it's talking about sdc. /dev/disk/by-uuid/ contains .. lrwxrwxrwx 1 root root 9 2007-07-17 20:35 2d773baf-8174-10a6-14db-a78e0e676e89 -> ../../sdd lrwxrwxrwx 1 root root 10 2007-07-20 18:44 3B69-1AFD -> ../../sdl1 lrwxrwxrwx 1 root root 10 2007-07-20 19:06 46A1-3FCB -> ../../sdi1 lrwxrwxrwx 1 root root 10 2007-07-17 20:35 4e728818-fcf1-21ee-07a5-302b72bc6129 -> ../../sdc1 lrwxrwxrwx 1 root root 10 2007-07-17 20:35 5f435361-5797-4a8c-a285-c72fa455d401 -> ../../sda1 lrwxrwxrwx 1 root root 9 2007-07-17 20:35 9502a546-dd98-41df-8916-45032d801b69 -> ../../md0 lrwxrwxrwx 1 root root 10 2007-07-17 20:35 ed102ac9-5615-c34b-5fe7-1a9029705ebf -> ../../sda2 note that uuid matches sdd instead. > And what does: > udevtest /block/sdc > print? parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules file parse_file: reading '/etc/udev/rules.d/40-multipath.rules' as rules file parse_file: reading '/etc/udev/rules.d/50-udev.rules' as rules file parse_file: reading '/etc/udev/rules.d/60-libsane.rules' as rules file parse_file: reading '/etc/udev/rules.d/60-net.rules' as rules file parse_file: reading '/etc/udev/rules.d/60-pcmcia.rules' as rules file parse_file: reading '/etc/udev/rules.d/60-wacom.rules' as rules file parse_file: reading '/etc/udev/rules.d/85-pcscd_ccid.rules' as rules file parse_file: reading '/etc/udev/rules.d/85-pcscd_egate.rules' as rules file parse_file: reading '/etc/udev/rules.d/90-alsa.rules' as rules file parse_file: reading '/etc/udev/rules.d/90-hal.rules' as rules file parse_file: reading '/etc/udev/rules.d/95-pam-console.rules' as rules file parse_file: reading '/etc/udev/rules.d/bluetooth.rules' as rules file This program is for debugging only, it does not create any node, or run any program specified by a RUN key. It may show incorrect results, if rules match against subsystem specfic kernel event variables. main: looking at device '/block/sdc' from subsystem 'block' run_program: '/bin/bash -c '/sbin/lsmod | /bin/grep ^dm_multipath'' run_program: '/bin/bash' (stdout) 'dm_multipath 28889 0 ' run_program: '/bin/bash' returned with status 0 run_program: '/lib/udev/usb_id -x' run_program: '/lib/udev/usb_id' returned with status 1 run_program: '/lib/udev/scsi_id -g -x -s /block/sdc -d /dev/.tmp-8-32' run_program: '/lib/udev/scsi_id' (stdout) 'ID_VENDOR=ATA' run_program: '/lib/udev/scsi_id' (stdout) 'ID_MODEL=WDC_WD2500KS-00M' run_program: '/lib/udev/scsi_id' (stdout) 'ID_REVISION=02.0' run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL=SATA_WDC_WD2500KS-00_WD-WCANK6187088' run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL_SHORT=WD-WCANK6187088' run_program: '/lib/udev/scsi_id' (stdout) 'ID_TYPE=disk' run_program: '/lib/udev/scsi_id' (stdout) 'ID_BUS=scsi' run_program: '/lib/udev/scsi_id' returned with status 0 udev_rules_get_name: add symlink 'disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6187088' run_program: '/lib/udev/path_id /block/sdc' run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=pci-0000:05:05.0-scsi-0:0:0:0' run_program: '/lib/udev/path_id' returned with status 0 udev_rules_get_name: add symlink 'disk/by-path/pci-0000:05:05.0-scsi-0:0:0:0' run_program: '/lib/udev/vol_id --export /dev/.tmp-8-32' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_USAGE=raid' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_TYPE=linux_raid_member' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_VERSION=0.90.0' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_UUID=2d773baf-8174-10a6-14db-a78e0e676e89' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL=' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL_SAFE=' run_program: '/lib/udev/vol_id' returned with status 0 udev_rules_get_name: add symlink 'disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' run_program: '/lib/udev/edd_id --export /dev/.tmp-8-32' run_program: '/lib/udev/edd_id' (stderr) 'no kernel EDD support' run_program: '/lib/udev/edd_id' returned with status 2 udev_rules_get_name: no node name set, will use kernel name 'sdc' udev_device_event: device '/block/sdc' already in database, validate currently present symlinks udev_node_add: creating device node '/dev/sdc', major = '8', minor = '32', mode = '0640', uid = '0', gid = '6' udev_node_add: creating symlink '/dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6187088' to '../../sdc' udev_node_add: creating symlink '/dev/disk/by-path/pci-0000:05:05.0-scsi-0:0:0:0' to '../../sdc' udev_node_add: creating symlink '/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' to '../../sdc' main: run: '/sbin/multipath -v0 8:32' main: run: 'socket:/org/kernel/udev/monitor' main: run: 'socket:/org/freedesktop/hal/udev_event' main: run: '/sbin/pam_console_apply /dev/sdc /dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6187088 /dev/disk/by-path/pci-0000:05:05.0-scsi-0:0:0:0 /dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' running udevtest on sdd gets me .. parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules file parse_file: reading '/etc/udev/rules.d/40-multipath.rules' as rules file parse_file: reading '/etc/udev/rules.d/50-udev.rules' as rules file parse_file: reading '/etc/udev/rules.d/60-libsane.rules' as rules file parse_file: reading '/etc/udev/rules.d/60-net.rules' as rules file parse_file: reading '/etc/udev/rules.d/60-pcmcia.rules' as rules file parse_file: reading '/etc/udev/rules.d/60-wacom.rules' as rules file parse_file: reading '/etc/udev/rules.d/85-pcscd_ccid.rules' as rules file parse_file: reading '/etc/udev/rules.d/85-pcscd_egate.rules' as rules file parse_file: reading '/etc/udev/rules.d/90-alsa.rules' as rules file parse_file: reading '/etc/udev/rules.d/90-hal.rules' as rules file parse_file: reading '/etc/udev/rules.d/95-pam-console.rules' as rules file parse_file: reading '/etc/udev/rules.d/bluetooth.rules' as rules file This program is for debugging only, it does not create any node, or run any program specified by a RUN key. It may show incorrect results, if rules match against subsystem specfic kernel event variables. main: looking at device '/block/sdd' from subsystem 'block' run_program: '/bin/bash -c '/sbin/lsmod | /bin/grep ^dm_multipath'' run_program: '/bin/bash' (stdout) 'dm_multipath 28889 0 ' run_program: '/bin/bash' returned with status 0 run_program: '/lib/udev/usb_id -x' run_program: '/lib/udev/usb_id' returned with status 1 run_program: '/lib/udev/scsi_id -g -x -s /block/sdd -d /dev/.tmp-8-48' run_program: '/lib/udev/scsi_id' (stdout) 'ID_VENDOR=ATA' run_program: '/lib/udev/scsi_id' (stdout) 'ID_MODEL=WDC_WD2500KS-00M' run_program: '/lib/udev/scsi_id' (stdout) 'ID_REVISION=02.0' run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL=SATA_WDC_WD2500KS-00_WD-WCANK6240588' run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL_SHORT=WD-WCANK6240588' run_program: '/lib/udev/scsi_id' (stdout) 'ID_TYPE=disk' run_program: '/lib/udev/scsi_id' (stdout) 'ID_BUS=scsi' run_program: '/lib/udev/scsi_id' returned with status 0 udev_rules_get_name: add symlink 'disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6240588' run_program: '/lib/udev/path_id /block/sdd' run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=pci-0000:05:05.0-scsi-1:0:0:0' run_program: '/lib/udev/path_id' returned with status 0 udev_rules_get_name: add symlink 'disk/by-path/pci-0000:05:05.0-scsi-1:0:0:0' run_program: '/lib/udev/vol_id --export /dev/.tmp-8-48' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_USAGE=raid' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_TYPE=linux_raid_member' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_VERSION=0.90.0' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_UUID=2d773baf-8174-10a6-14db-a78e0e676e89' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL=' run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL_SAFE=' run_program: '/lib/udev/vol_id' returned with status 0 udev_rules_get_name: add symlink 'disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' run_program: '/lib/udev/edd_id --export /dev/.tmp-8-48' run_program: '/lib/udev/edd_id' (stderr) 'no kernel EDD support' run_program: '/lib/udev/edd_id' returned with status 2 udev_rules_get_name: no node name set, will use kernel name 'sdd' udev_device_event: device '/block/sdd' already in database, validate currently present symlinks udev_node_add: creating device node '/dev/sdd', major = '8', minor = '48', mode = '0640', uid = '0', gid = '6' udev_node_add: creating symlink '/dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6240588' to '../../sdd' udev_node_add: creating symlink '/dev/disk/by-path/pci-0000:05:05.0-scsi-1:0:0:0' to '../../sdd' udev_node_add: creating symlink '/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' to '../../sdd' main: run: '/sbin/multipath -v0 8:48' main: run: 'socket:/org/kernel/udev/monitor' main: run: 'socket:/org/freedesktop/hal/udev_event' main: run: '/sbin/pam_console_apply /dev/sdd /dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6240588 /dev/disk/by-path/pci-0000:05:05.0-scsi-1:0:0:0 /dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' note, same uuid. wtf? Dave -- http://www.codemonkey.org.uk ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: film at 11: kernel update breaks udev. 2007-07-21 1:36 ` Dave Jones @ 2007-07-21 1:55 ` Kay Sievers 2007-07-21 2:20 ` Kay Sievers 0 siblings, 1 reply; 7+ messages in thread From: Kay Sievers @ 2007-07-21 1:55 UTC (permalink / raw) To: Dave Jones, Kay Sievers, Linux Kernel On 7/21/07, Dave Jones <davej@redhat.com> wrote: > On Sat, Jul 21, 2007 at 03:28:12AM +0200, Kay Sievers wrote: > > On 7/21/07, Dave Jones <davej@redhat.com> wrote: > > > On Sat, Jul 21, 2007 at 03:09:55AM +0200, Kay Sievers wrote: > > > > On 7/21/07, Dave Jones <davej@redhat.com> wrote: > > > > > Just one of my machines to 2.6.22.1, and got this during boot.. > > > > > > > > > > Starting udev: udevd-event[619]: udev_node_symlink: symlink(../../sdc/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89) failed: File exists > > > > > > > > > > Under 2.6.21, all was fine. > > > > > > > > > > sdc is one disk of a 3 disk raid5 set. > > > > > The raidset still manages to come up despite this. > > > > > > > > > > This is a Fedora 7 box, with udev-106-4.1.fc7 > > > > > > > > > > What changed this time? > > > > > > > > CONFIG_BLK_DEV_BSG=y? > > > > > > > > There's a name-clash, because bsg tries to create devices with the same name. > > > > James sent a patch, it's on lkml. > > > > > > BSG isn't in 2.6.22 > > > > Ok. There has nothing else changed, that I could think of what could cause this. > > > > The code in udev that prints this message looks like: > > err("symlink(%s, %s) failed: %s", linktarget, filename, strerror(errno)); > > > > That doesn't really match what you posted. Are there chars missing? > > Umm. Now I'm confused. Note above that it's talking about sdc. > /dev/disk/by-uuid/ contains .. > > lrwxrwxrwx 1 root root 9 2007-07-17 20:35 2d773baf-8174-10a6-14db-a78e0e676e89 -> ../../sdd > lrwxrwxrwx 1 root root 10 2007-07-20 18:44 3B69-1AFD -> ../../sdl1 > lrwxrwxrwx 1 root root 10 2007-07-20 19:06 46A1-3FCB -> ../../sdi1 > lrwxrwxrwx 1 root root 10 2007-07-17 20:35 4e728818-fcf1-21ee-07a5-302b72bc6129 -> ../../sdc1 > lrwxrwxrwx 1 root root 10 2007-07-17 20:35 5f435361-5797-4a8c-a285-c72fa455d401 -> ../../sda1 > lrwxrwxrwx 1 root root 9 2007-07-17 20:35 9502a546-dd98-41df-8916-45032d801b69 -> ../../md0 > lrwxrwxrwx 1 root root 10 2007-07-17 20:35 ed102ac9-5615-c34b-5fe7-1a9029705ebf -> ../../sda2 > > note that uuid matches sdd instead. > > > And what does: > > udevtest /block/sdc > > print? > > parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules file > parse_file: reading '/etc/udev/rules.d/40-multipath.rules' as rules file > parse_file: reading '/etc/udev/rules.d/50-udev.rules' as rules file > parse_file: reading '/etc/udev/rules.d/60-libsane.rules' as rules file > parse_file: reading '/etc/udev/rules.d/60-net.rules' as rules file > parse_file: reading '/etc/udev/rules.d/60-pcmcia.rules' as rules file > parse_file: reading '/etc/udev/rules.d/60-wacom.rules' as rules file > parse_file: reading '/etc/udev/rules.d/85-pcscd_ccid.rules' as rules file > parse_file: reading '/etc/udev/rules.d/85-pcscd_egate.rules' as rules file > parse_file: reading '/etc/udev/rules.d/90-alsa.rules' as rules file > parse_file: reading '/etc/udev/rules.d/90-hal.rules' as rules file > parse_file: reading '/etc/udev/rules.d/95-pam-console.rules' as rules file > parse_file: reading '/etc/udev/rules.d/bluetooth.rules' as rules file > This program is for debugging only, it does not create any node, > or run any program specified by a RUN key. It may show incorrect results, > if rules match against subsystem specfic kernel event variables. > > main: looking at device '/block/sdc' from subsystem 'block' > run_program: '/bin/bash -c '/sbin/lsmod | /bin/grep ^dm_multipath'' > run_program: '/bin/bash' (stdout) 'dm_multipath 28889 0 ' > run_program: '/bin/bash' returned with status 0 > run_program: '/lib/udev/usb_id -x' > run_program: '/lib/udev/usb_id' returned with status 1 > run_program: '/lib/udev/scsi_id -g -x -s /block/sdc -d /dev/.tmp-8-32' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_VENDOR=ATA' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_MODEL=WDC_WD2500KS-00M' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_REVISION=02.0' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL=SATA_WDC_WD2500KS-00_WD-WCANK6187088' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL_SHORT=WD-WCANK6187088' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_TYPE=disk' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_BUS=scsi' > run_program: '/lib/udev/scsi_id' returned with status 0 > udev_rules_get_name: add symlink 'disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6187088' > run_program: '/lib/udev/path_id /block/sdc' > run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=pci-0000:05:05.0-scsi-0:0:0:0' > run_program: '/lib/udev/path_id' returned with status 0 > udev_rules_get_name: add symlink 'disk/by-path/pci-0000:05:05.0-scsi-0:0:0:0' > run_program: '/lib/udev/vol_id --export /dev/.tmp-8-32' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_USAGE=raid' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_TYPE=linux_raid_member' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_VERSION=0.90.0' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_UUID=2d773baf-8174-10a6-14db-a78e0e676e89' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL=' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL_SAFE=' > run_program: '/lib/udev/vol_id' returned with status 0 > udev_rules_get_name: add symlink 'disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' > run_program: '/lib/udev/edd_id --export /dev/.tmp-8-32' > run_program: '/lib/udev/edd_id' (stderr) 'no kernel EDD support' > run_program: '/lib/udev/edd_id' returned with status 2 > udev_rules_get_name: no node name set, will use kernel name 'sdc' > udev_device_event: device '/block/sdc' already in database, validate currently present symlinks > udev_node_add: creating device node '/dev/sdc', major = '8', minor = '32', mode = '0640', uid = '0', gid = '6' > udev_node_add: creating symlink '/dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6187088' to '../../sdc' > udev_node_add: creating symlink '/dev/disk/by-path/pci-0000:05:05.0-scsi-0:0:0:0' to '../../sdc' > udev_node_add: creating symlink '/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' to '../../sdc' > main: run: '/sbin/multipath -v0 8:32' > main: run: 'socket:/org/kernel/udev/monitor' > main: run: 'socket:/org/freedesktop/hal/udev_event' > main: run: '/sbin/pam_console_apply /dev/sdc /dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6187088 /dev/disk/by-path/pci-0000:05:05.0-scsi-0:0:0:0 /dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' > > > > running udevtest on sdd gets me .. > > parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules file > parse_file: reading '/etc/udev/rules.d/40-multipath.rules' as rules file > parse_file: reading '/etc/udev/rules.d/50-udev.rules' as rules file > parse_file: reading '/etc/udev/rules.d/60-libsane.rules' as rules file > parse_file: reading '/etc/udev/rules.d/60-net.rules' as rules file > parse_file: reading '/etc/udev/rules.d/60-pcmcia.rules' as rules file > parse_file: reading '/etc/udev/rules.d/60-wacom.rules' as rules file > parse_file: reading '/etc/udev/rules.d/85-pcscd_ccid.rules' as rules file > parse_file: reading '/etc/udev/rules.d/85-pcscd_egate.rules' as rules file > parse_file: reading '/etc/udev/rules.d/90-alsa.rules' as rules file > parse_file: reading '/etc/udev/rules.d/90-hal.rules' as rules file > parse_file: reading '/etc/udev/rules.d/95-pam-console.rules' as rules file > parse_file: reading '/etc/udev/rules.d/bluetooth.rules' as rules file > This program is for debugging only, it does not create any node, > or run any program specified by a RUN key. It may show incorrect results, > if rules match against subsystem specfic kernel event variables. > > main: looking at device '/block/sdd' from subsystem 'block' > run_program: '/bin/bash -c '/sbin/lsmod | /bin/grep ^dm_multipath'' > run_program: '/bin/bash' (stdout) 'dm_multipath 28889 0 ' > run_program: '/bin/bash' returned with status 0 > run_program: '/lib/udev/usb_id -x' > run_program: '/lib/udev/usb_id' returned with status 1 > run_program: '/lib/udev/scsi_id -g -x -s /block/sdd -d /dev/.tmp-8-48' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_VENDOR=ATA' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_MODEL=WDC_WD2500KS-00M' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_REVISION=02.0' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL=SATA_WDC_WD2500KS-00_WD-WCANK6240588' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL_SHORT=WD-WCANK6240588' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_TYPE=disk' > run_program: '/lib/udev/scsi_id' (stdout) 'ID_BUS=scsi' > run_program: '/lib/udev/scsi_id' returned with status 0 > udev_rules_get_name: add symlink 'disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6240588' > run_program: '/lib/udev/path_id /block/sdd' > run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=pci-0000:05:05.0-scsi-1:0:0:0' > run_program: '/lib/udev/path_id' returned with status 0 > udev_rules_get_name: add symlink 'disk/by-path/pci-0000:05:05.0-scsi-1:0:0:0' > run_program: '/lib/udev/vol_id --export /dev/.tmp-8-48' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_USAGE=raid' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_TYPE=linux_raid_member' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_VERSION=0.90.0' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_UUID=2d773baf-8174-10a6-14db-a78e0e676e89' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL=' > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL_SAFE=' > run_program: '/lib/udev/vol_id' returned with status 0 > udev_rules_get_name: add symlink 'disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' > run_program: '/lib/udev/edd_id --export /dev/.tmp-8-48' > run_program: '/lib/udev/edd_id' (stderr) 'no kernel EDD support' > run_program: '/lib/udev/edd_id' returned with status 2 > udev_rules_get_name: no node name set, will use kernel name 'sdd' > udev_device_event: device '/block/sdd' already in database, validate currently present symlinks > udev_node_add: creating device node '/dev/sdd', major = '8', minor = '48', mode = '0640', uid = '0', gid = '6' > udev_node_add: creating symlink '/dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6240588' to '../../sdd' > udev_node_add: creating symlink '/dev/disk/by-path/pci-0000:05:05.0-scsi-1:0:0:0' to '../../sdd' > udev_node_add: creating symlink '/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' to '../../sdd' > main: run: '/sbin/multipath -v0 8:48' > main: run: 'socket:/org/kernel/udev/monitor' > main: run: 'socket:/org/freedesktop/hal/udev_event' > main: run: '/sbin/pam_console_apply /dev/sdd /dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6240588 /dev/disk/by-path/pci-0000:05:05.0-scsi-1:0:0:0 /dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' > > > note, same uuid. wtf? The devices are competing about the same symlink, because they contain the same metadata. But all of them are USAGE="raid" which should not create any uuid-links at all. Let's look at your rules, what does: grep by-uuid /etc/udev/rules.d/*.rules print? Kay ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: film at 11: kernel update breaks udev. 2007-07-21 1:55 ` Kay Sievers @ 2007-07-21 2:20 ` Kay Sievers 0 siblings, 0 replies; 7+ messages in thread From: Kay Sievers @ 2007-07-21 2:20 UTC (permalink / raw) To: Dave Jones, Kay Sievers, Linux Kernel On 7/21/07, Kay Sievers <kay.sievers@vrfy.org> wrote: > On 7/21/07, Dave Jones <davej@redhat.com> wrote: > > On Sat, Jul 21, 2007 at 03:28:12AM +0200, Kay Sievers wrote: > > > On 7/21/07, Dave Jones <davej@redhat.com> wrote: > > > > On Sat, Jul 21, 2007 at 03:09:55AM +0200, Kay Sievers wrote: > > > > > On 7/21/07, Dave Jones <davej@redhat.com> wrote: > > > > > > Just one of my machines to 2.6.22.1, and got this during boot.. > > > > > > > > > > > > Starting udev: udevd-event[619]: udev_node_symlink: symlink(../../sdc/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89) failed: File exists > > > > > > > > > > > > Under 2.6.21, all was fine. > > > > > > > > > > > > sdc is one disk of a 3 disk raid5 set. > > > > > > The raidset still manages to come up despite this. > > > > > > > > > > > > This is a Fedora 7 box, with udev-106-4.1.fc7 > > > > > > > > > > > > What changed this time? > > > > > > > > > > CONFIG_BLK_DEV_BSG=y? > > > > > > > > > > There's a name-clash, because bsg tries to create devices with the same name. > > > > > James sent a patch, it's on lkml. > > > > > > > > BSG isn't in 2.6.22 > > > > > > Ok. There has nothing else changed, that I could think of what could cause this. > > > > > > The code in udev that prints this message looks like: > > > err("symlink(%s, %s) failed: %s", linktarget, filename, strerror(errno)); > > > > > > That doesn't really match what you posted. Are there chars missing? > > > > Umm. Now I'm confused. Note above that it's talking about sdc. > > /dev/disk/by-uuid/ contains .. > > > > lrwxrwxrwx 1 root root 9 2007-07-17 20:35 2d773baf-8174-10a6-14db-a78e0e676e89 -> ../../sdd > > lrwxrwxrwx 1 root root 10 2007-07-20 18:44 3B69-1AFD -> ../../sdl1 > > lrwxrwxrwx 1 root root 10 2007-07-20 19:06 46A1-3FCB -> ../../sdi1 > > lrwxrwxrwx 1 root root 10 2007-07-17 20:35 4e728818-fcf1-21ee-07a5-302b72bc6129 -> ../../sdc1 > > lrwxrwxrwx 1 root root 10 2007-07-17 20:35 5f435361-5797-4a8c-a285-c72fa455d401 -> ../../sda1 > > lrwxrwxrwx 1 root root 9 2007-07-17 20:35 9502a546-dd98-41df-8916-45032d801b69 -> ../../md0 > > lrwxrwxrwx 1 root root 10 2007-07-17 20:35 ed102ac9-5615-c34b-5fe7-1a9029705ebf -> ../../sda2 > > > > note that uuid matches sdd instead. > > > > > And what does: > > > udevtest /block/sdc > > > print? > > > > parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/40-multipath.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/50-udev.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/60-libsane.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/60-net.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/60-pcmcia.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/60-wacom.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/85-pcscd_ccid.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/85-pcscd_egate.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/90-alsa.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/90-hal.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/95-pam-console.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/bluetooth.rules' as rules file > > This program is for debugging only, it does not create any node, > > or run any program specified by a RUN key. It may show incorrect results, > > if rules match against subsystem specfic kernel event variables. > > > > main: looking at device '/block/sdc' from subsystem 'block' > > run_program: '/bin/bash -c '/sbin/lsmod | /bin/grep ^dm_multipath'' > > run_program: '/bin/bash' (stdout) 'dm_multipath 28889 0 ' > > run_program: '/bin/bash' returned with status 0 > > run_program: '/lib/udev/usb_id -x' > > run_program: '/lib/udev/usb_id' returned with status 1 > > run_program: '/lib/udev/scsi_id -g -x -s /block/sdc -d /dev/.tmp-8-32' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_VENDOR=ATA' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_MODEL=WDC_WD2500KS-00M' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_REVISION=02.0' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL=SATA_WDC_WD2500KS-00_WD-WCANK6187088' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL_SHORT=WD-WCANK6187088' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_TYPE=disk' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_BUS=scsi' > > run_program: '/lib/udev/scsi_id' returned with status 0 > > udev_rules_get_name: add symlink 'disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6187088' > > run_program: '/lib/udev/path_id /block/sdc' > > run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=pci-0000:05:05.0-scsi-0:0:0:0' > > run_program: '/lib/udev/path_id' returned with status 0 > > udev_rules_get_name: add symlink 'disk/by-path/pci-0000:05:05.0-scsi-0:0:0:0' > > run_program: '/lib/udev/vol_id --export /dev/.tmp-8-32' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_USAGE=raid' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_TYPE=linux_raid_member' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_VERSION=0.90.0' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_UUID=2d773baf-8174-10a6-14db-a78e0e676e89' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL=' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL_SAFE=' > > run_program: '/lib/udev/vol_id' returned with status 0 > > udev_rules_get_name: add symlink 'disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' > > run_program: '/lib/udev/edd_id --export /dev/.tmp-8-32' > > run_program: '/lib/udev/edd_id' (stderr) 'no kernel EDD support' > > run_program: '/lib/udev/edd_id' returned with status 2 > > udev_rules_get_name: no node name set, will use kernel name 'sdc' > > udev_device_event: device '/block/sdc' already in database, validate currently present symlinks > > udev_node_add: creating device node '/dev/sdc', major = '8', minor = '32', mode = '0640', uid = '0', gid = '6' > > udev_node_add: creating symlink '/dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6187088' to '../../sdc' > > udev_node_add: creating symlink '/dev/disk/by-path/pci-0000:05:05.0-scsi-0:0:0:0' to '../../sdc' > > udev_node_add: creating symlink '/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' to '../../sdc' > > main: run: '/sbin/multipath -v0 8:32' > > main: run: 'socket:/org/kernel/udev/monitor' > > main: run: 'socket:/org/freedesktop/hal/udev_event' > > main: run: '/sbin/pam_console_apply /dev/sdc /dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6187088 /dev/disk/by-path/pci-0000:05:05.0-scsi-0:0:0:0 /dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' > > > > > > > > running udevtest on sdd gets me .. > > > > parse_file: reading '/etc/udev/rules.d/05-udev-early.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/40-multipath.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/50-udev.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/60-libsane.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/60-net.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/60-pcmcia.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/60-wacom.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/85-pcscd_ccid.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/85-pcscd_egate.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/90-alsa.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/90-hal.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/95-pam-console.rules' as rules file > > parse_file: reading '/etc/udev/rules.d/bluetooth.rules' as rules file > > This program is for debugging only, it does not create any node, > > or run any program specified by a RUN key. It may show incorrect results, > > if rules match against subsystem specfic kernel event variables. > > > > main: looking at device '/block/sdd' from subsystem 'block' > > run_program: '/bin/bash -c '/sbin/lsmod | /bin/grep ^dm_multipath'' > > run_program: '/bin/bash' (stdout) 'dm_multipath 28889 0 ' > > run_program: '/bin/bash' returned with status 0 > > run_program: '/lib/udev/usb_id -x' > > run_program: '/lib/udev/usb_id' returned with status 1 > > run_program: '/lib/udev/scsi_id -g -x -s /block/sdd -d /dev/.tmp-8-48' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_VENDOR=ATA' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_MODEL=WDC_WD2500KS-00M' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_REVISION=02.0' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL=SATA_WDC_WD2500KS-00_WD-WCANK6240588' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_SERIAL_SHORT=WD-WCANK6240588' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_TYPE=disk' > > run_program: '/lib/udev/scsi_id' (stdout) 'ID_BUS=scsi' > > run_program: '/lib/udev/scsi_id' returned with status 0 > > udev_rules_get_name: add symlink 'disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6240588' > > run_program: '/lib/udev/path_id /block/sdd' > > run_program: '/lib/udev/path_id' (stdout) 'ID_PATH=pci-0000:05:05.0-scsi-1:0:0:0' > > run_program: '/lib/udev/path_id' returned with status 0 > > udev_rules_get_name: add symlink 'disk/by-path/pci-0000:05:05.0-scsi-1:0:0:0' > > run_program: '/lib/udev/vol_id --export /dev/.tmp-8-48' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_USAGE=raid' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_TYPE=linux_raid_member' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_VERSION=0.90.0' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_UUID=2d773baf-8174-10a6-14db-a78e0e676e89' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL=' > > run_program: '/lib/udev/vol_id' (stdout) 'ID_FS_LABEL_SAFE=' > > run_program: '/lib/udev/vol_id' returned with status 0 > > udev_rules_get_name: add symlink 'disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' > > run_program: '/lib/udev/edd_id --export /dev/.tmp-8-48' > > run_program: '/lib/udev/edd_id' (stderr) 'no kernel EDD support' > > run_program: '/lib/udev/edd_id' returned with status 2 > > udev_rules_get_name: no node name set, will use kernel name 'sdd' > > udev_device_event: device '/block/sdd' already in database, validate currently present symlinks > > udev_node_add: creating device node '/dev/sdd', major = '8', minor = '48', mode = '0640', uid = '0', gid = '6' > > udev_node_add: creating symlink '/dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6240588' to '../../sdd' > > udev_node_add: creating symlink '/dev/disk/by-path/pci-0000:05:05.0-scsi-1:0:0:0' to '../../sdd' > > udev_node_add: creating symlink '/dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' to '../../sdd' > > main: run: '/sbin/multipath -v0 8:48' > > main: run: 'socket:/org/kernel/udev/monitor' > > main: run: 'socket:/org/freedesktop/hal/udev_event' > > main: run: '/sbin/pam_console_apply /dev/sdd /dev/disk/by-id/scsi-SATA_WDC_WD2500KS-00_WD-WCANK6240588 /dev/disk/by-path/pci-0000:05:05.0-scsi-1:0:0:0 /dev/disk/by-uuid/2d773baf-8174-10a6-14db-a78e0e676e89' > > > > > > note, same uuid. wtf? > > The devices are competing about the same symlink, because they contain > the same metadata. But all of them are USAGE="raid" which should not > create any uuid-links at all. > > Let's look at your rules, what does: > grep by-uuid /etc/udev/rules.d/*.rules > print? Oh, looking at the current Fedora udev rules, they are just not correct. You are rolling your own version of the persistent link rules which don't do what they should. I strongly suggest to use the default rules instead of rolling your own incomplete copy of it. The warning is harmless, you can just ignore it, it's a failing link creation for a raid-set-metadata uuid, not a filesystem uuid. These links would be just skipped with normal udev rules. Thanks, Kay ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2007-07-21 2:21 UTC | newest] Thread overview: 7+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2007-07-21 1:04 film at 11: kernel update breaks udev Dave Jones 2007-07-21 1:09 ` Kay Sievers 2007-07-21 1:16 ` Dave Jones 2007-07-21 1:28 ` Kay Sievers 2007-07-21 1:36 ` Dave Jones 2007-07-21 1:55 ` Kay Sievers 2007-07-21 2:20 ` Kay Sievers
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox