Hi,

I've written a couple of udev.rules that should identify 2 disks using the UUID obtained from scsi_id. I have been running udev.debug and checking the debug information out to /var/log/messages and I find that the output from scsi_id never matches my RESULT ... even though i think it should.

So here are the rules:
BUS="scsi", PROGRAM="/sbin/scsi_id -g -s /block/%k", RESULT="200000e1100a35065", NAME="disk-sda%n"

BUS="scsi", RESULT="200000e1100a34fef", NAME="disk-sdb%n"
BUS="scsi", RESULT="3600508b4000151bf0001e000015b0000", NAME="sues-sdc", SYMLINK="tester"
BUS="scsi", RESULT="3600508b4000151bf0001e00001610000", NAME="sues-sdd"

And here are a few of the lines from the messages file ...

Jun 23 01:04:00 rx1620-1 udev[12450]: namedev_name_device: process rule
Jun 23 01:04:00 rx1620-1 udev[12450]: match_rule: check for BUS dev->bus='scsi' sysfs_device->bus='scsi'
Jun 23 01:04:00 rx1620-1 udev[12450]: match_rule: BUS matches
Jun 23 01:04:00 rx1620-1 udev[12450]: match_rule: check for RESULT dev->result='3600508b4000151bf0001e00001610000', udev->program_result='3600508b4000151bf0001e00001610000 '
Jun 23 01:04:00 rx1620-1 udev[12450]: match_rule: RESULT is not matching

As can be seen from the log it looks like there is some space or \n or something being put at the end of the string in program_result and that is the reason that there is no match. But surely everybody is using scsi_id in this way aren't they ? BTW if it helps any, on on SLES9 (still without SP1) with all the udev stuff that comes with it...

Any ideas what's going wrong here ?
thanks and regards,
Sue

Lycos email has now 300 Megabytes of free storage... Get it now at mail.lycos.co.uk