I am new to working with udev. I have set up an openfiler server with a raid array (md0) which is established as an iscsi target and esata drive for backup. For backup, I would like to connect to the iscsi target using open-iscsi initiator and then dd from the iscsi to the esata drive. I am concerned that the mapping won't always be the same in udev (i.e. iscsi currently sde and esata is sdd)
I tried to write the following udev rule:
so that the iscsi always comes in on /dev/iscsi/share_drive and the eSATA drive is /dev/backup. It appears that since I am defining the rule based on the BUS=="scsi" attributes instead of the block device, I do not get a clean block device in /dev/iscsi. Is there anyway to select the block device using these attributes. Right now if I look at the /dev/backup, it appears to show information for the parent bus instead of the drive.
Also, I would note that openfiler is based on rLinux and does not seem to have persistent devices (at least there is no /dev/disk folder).
Any help would be appreciated.
- flub
I tried to write the following udev rule:
Code:
SUBSYSTEM=="block", BUS=="scsi", SYSFS{vendor}=="OPNFILER", NAME="iscsi/share_drive"
SUBSYSTEM=="block", BUS=="scsi", SYSFS{model}=="WDCWD10EAVS-00D", NAME="backup"
Also, I would note that openfiler is based on rLinux and does not seem to have persistent devices (at least there is no /dev/disk folder).
Any help would be appreciated.
- flub