Re: Problems using scsi_id with udevstart

[Andrew Patterson <andrew.patterson@hp.com>]

[-- Attachment #1: Type: text/plain, Size: 3462 bytes --]

On Tue, 2004-10-05 at 16:53 -0700, Patrick Mansfield wrote:
> I don't know much about how udevstart operates. Anyway ...
> 
> On Tue, Oct 05, 2004 at 05:33:46PM -0600, Andrew Patterson wrote:
> > Hi,
> > 
> > I added the following udev rule to make human-readable device file names
> > for my SCSI disks:
> > 
> > BUS="scsi", KERNEL="sd*", PROGRAM="scsi_id", NAME="scsi_disks/%c-%b",
> > SYMLINK="%k"
> 
> Interesting ... I was thinking of the opposite type of rule to match some
> of the SUSE device naming, like:
> 
> BUS="scsi", KERNEL="sd*", PROGRAM="scsi_id", NAME="%k" SYMLINK="scsi_disks/%c-%b", 
> 

Yes, I think this is better as well.  Better to have the real node as
the kernel name and the symlinks to the human-readable stuff.

> > When I run udevstart, I get the following errors in the logfile:
> > 
> > Oct  5 17:25:17 natasha udevstart: PROGRAM execution of 'scsi_id' failed
> > Oct  5 17:25:17 natasha udevstart: creating device node '/dev/sdy2'
> > Oct  5 17:25:17 natasha udevstart: PROGRAM execution of 'scsi_id' failed
> > Oct  5 17:25:17 natasha udevstart: creating device node '/dev/sdz'
> > 
> > scsi_id is failing because no parameters are being passed to it, and I
> > think DEVPATH is also not being set appropriately.  Here is debug
> > output:
> > 
> > get_sysfs_device: device 2:0:0:0 is registered with bus 'scsi'
> > namedev_name_device: sysfs_device-
> > >path='/sys/devices/pci0000:20/0000:20:01.0/host2/2:0:0:0'
> > namedev_name_device: sysfs_device->bus_id='2:0:0:0'
> > namedev_name_device: sysfs_device->bus='scsi'
> > wait_for_device_to_initialize: looking for file 'vendor' on bus 'scsi'
> > namedev_name_device: class_dev->name = 'sda'
> > namedev_name_device: udev->kernel_name = 'sda'
> > namedev_name_device: kernel_number=''
> > namedev_name_device: process rule
> > match_rule: check for BUS dev->bus='scsi' sysfs_device->bus='scsi'
> > match_rule: BUS matches
> > match_rule: check PROGRAM
> > execute_program: 
> > 
> > execute_program: result len 256 too short
> > execute_program: result is ' matching
> 

As Kay mentioned, I need the full path to scsi_id.  When using the full
path you get the following:

match_rule: check for BUS dev->bus='scsi' sysfs_device->bus='scsi'
match_rule: BUS matches
match_rule: check for KERNEL dev->kernel='sd*' class_dev->name='sda'
match_rule: KERNEL matches
match_rule: check PROGRAM
execute_program: path = /sbin/scsi_id

execute_program: result is ''
execute_program: exec program status 0x100
match_rule: PROGRAM returned nonzero
match_rule: try parent sysfs device


Note: here is the error you get when scsi_id is run without any
parameters:

# /sbin/scsi_id
-s must be specified


> The above indicates udev thinks the output of scsi_id is too long.
> 
> [elm3b79 udev-bk]$ grep NAME_SIZE *.[hc] udev.h | grep define
> logging.h:#define LOGNAME_SIZE                  42
> udev.h:#define NAME_SIZE                        256
> udev.h:#define NAME_SIZE                        256
> 
> Greg or Kay, can you verify the above? Should we / can we increase
> NAME_SIZE?
> 
> Andrew - what does running scsi_id from the command line return for the
> device? Like this:
> 	
> 	scsi_id -s /block/sdN
> 

# /sbin/scsi_id -s  /block/sda
2000c50fffe33f611

I have -g set in /etc/scsi_id.conf

Andrew

> -- Patrick Mansfield
> 
-- 
Andrew Patterson                
Hewlett-Packard

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]