Archive-Team
/
zfs
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases 103 Wiki Activity
zfs/scripts/udev-rules/99-zpool.rules.dragon

332 lines
28 KiB
Plaintext
Raw Normal View History

Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
#
# /etc/udev/rules.d/99-zpool.rules
#
ENV{DEVTYPE}=="disk", IMPORT{program}="path_id %p"
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
# Full devices (*:pci*port:*:id-lun)
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:3-lun0", SYMLINK+="disk/zpool/a1"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:4-lun0", SYMLINK+="disk/zpool/a2"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:5-lun0", SYMLINK+="disk/zpool/a3"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:6-lun0", SYMLINK+="disk/zpool/a4"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:7-lun0", SYMLINK+="disk/zpool/a5"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:8-lun0", SYMLINK+="disk/zpool/a6"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:9-lun0", SYMLINK+="disk/zpool/a7"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:10-lun0", SYMLINK+="disk/zpool/a8"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:11-lun0", SYMLINK+="disk/zpool/a9"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:12-lun0", SYMLINK+="disk/zpool/a10"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:13-lun0", SYMLINK+="disk/zpool/a11"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:14-lun0", SYMLINK+="disk/zpool/a12"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:15-lun0", SYMLINK+="disk/zpool/a13"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:16-lun0", SYMLINK+="disk/zpool/a14"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*0:*:17-lun0", SYMLINK+="disk/zpool/a15"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:3-lun0", SYMLINK+="disk/zpool/b1"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:4-lun0", SYMLINK+="disk/zpool/b2"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:5-lun0", SYMLINK+="disk/zpool/b3"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:6-lun0", SYMLINK+="disk/zpool/b4"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:7-lun0", SYMLINK+="disk/zpool/b5"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:8-lun0", SYMLINK+="disk/zpool/b6"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:9-lun0", SYMLINK+="disk/zpool/b7"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:10-lun0", SYMLINK+="disk/zpool/b8"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:11-lun0", SYMLINK+="disk/zpool/b9"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:12-lun0", SYMLINK+="disk/zpool/b10"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:13-lun0", SYMLINK+="disk/zpool/b11"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:14-lun0", SYMLINK+="disk/zpool/b12"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:15-lun0", SYMLINK+="disk/zpool/b13"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:16-lun0", SYMLINK+="disk/zpool/b14"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:03:00.0*4:*:17-lun0", SYMLINK+="disk/zpool/b15"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:3-lun0", SYMLINK+="disk/zpool/c1"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:4-lun0", SYMLINK+="disk/zpool/c2"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:5-lun0", SYMLINK+="disk/zpool/c3"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:6-lun0", SYMLINK+="disk/zpool/c4"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:7-lun0", SYMLINK+="disk/zpool/c5"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:8-lun0", SYMLINK+="disk/zpool/c6"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:9-lun0", SYMLINK+="disk/zpool/c7"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:10-lun0", SYMLINK+="disk/zpool/c8"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:11-lun0", SYMLINK+="disk/zpool/c9"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:12-lun0", SYMLINK+="disk/zpool/c10"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:13-lun0", SYMLINK+="disk/zpool/c11"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:14-lun0", SYMLINK+="disk/zpool/c12"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:15-lun0", SYMLINK+="disk/zpool/c13"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:16-lun0", SYMLINK+="disk/zpool/c14"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*0:*:17-lun0", SYMLINK+="disk/zpool/c15"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:3-lun0", SYMLINK+="disk/zpool/d1"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:4-lun0", SYMLINK+="disk/zpool/d2"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:5-lun0", SYMLINK+="disk/zpool/d3"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:6-lun0", SYMLINK+="disk/zpool/d4"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:7-lun0", SYMLINK+="disk/zpool/d5"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:8-lun0", SYMLINK+="disk/zpool/d6"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:9-lun0", SYMLINK+="disk/zpool/d7"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:10-lun0", SYMLINK+="disk/zpool/d8"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:11-lun0", SYMLINK+="disk/zpool/d9"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:12-lun0", SYMLINK+="disk/zpool/d10"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:13-lun0", SYMLINK+="disk/zpool/d11"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:14-lun0", SYMLINK+="disk/zpool/d12"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:15-lun0", SYMLINK+="disk/zpool/d13"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:16-lun0", SYMLINK+="disk/zpool/d14"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:04:00.0*4:*:17-lun0", SYMLINK+="disk/zpool/d15"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:3-lun0", SYMLINK+="disk/zpool/e1"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:4-lun0", SYMLINK+="disk/zpool/e2"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:5-lun0", SYMLINK+="disk/zpool/e3"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:6-lun0", SYMLINK+="disk/zpool/e4"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:7-lun0", SYMLINK+="disk/zpool/e5"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:8-lun0", SYMLINK+="disk/zpool/e6"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:9-lun0", SYMLINK+="disk/zpool/e7"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:10-lun0", SYMLINK+="disk/zpool/e8"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:11-lun0", SYMLINK+="disk/zpool/e9"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:12-lun0", SYMLINK+="disk/zpool/e10"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:13-lun0", SYMLINK+="disk/zpool/e11"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:14-lun0", SYMLINK+="disk/zpool/e12"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:15-lun0", SYMLINK+="disk/zpool/e13"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:16-lun0", SYMLINK+="disk/zpool/e14"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*0:*:17-lun0", SYMLINK+="disk/zpool/e15"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:3-lun0", SYMLINK+="disk/zpool/f1"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:4-lun0", SYMLINK+="disk/zpool/f2"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:5-lun0", SYMLINK+="disk/zpool/f3"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:6-lun0", SYMLINK+="disk/zpool/f4"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:7-lun0", SYMLINK+="disk/zpool/f5"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:8-lun0", SYMLINK+="disk/zpool/f6"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:9-lun0", SYMLINK+="disk/zpool/f7"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:10-lun0", SYMLINK+="disk/zpool/f8"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:11-lun0", SYMLINK+="disk/zpool/f9"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:12-lun0", SYMLINK+="disk/zpool/f10"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:13-lun0", SYMLINK+="disk/zpool/f11"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:14-lun0", SYMLINK+="disk/zpool/f12"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:15-lun0", SYMLINK+="disk/zpool/f13"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:16-lun0", SYMLINK+="disk/zpool/f14"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:84:00.0*4:*:17-lun0", SYMLINK+="disk/zpool/f15"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:3-lun0", SYMLINK+="disk/zpool/g1"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:4-lun0", SYMLINK+="disk/zpool/g2"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:5-lun0", SYMLINK+="disk/zpool/g3"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:6-lun0", SYMLINK+="disk/zpool/g4"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:7-lun0", SYMLINK+="disk/zpool/g5"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:8-lun0", SYMLINK+="disk/zpool/g6"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:9-lun0", SYMLINK+="disk/zpool/g7"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:10-lun0", SYMLINK+="disk/zpool/g8"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:11-lun0", SYMLINK+="disk/zpool/g9"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:12-lun0", SYMLINK+="disk/zpool/g10"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:13-lun0", SYMLINK+="disk/zpool/g11"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:14-lun0", SYMLINK+="disk/zpool/g12"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:15-lun0", SYMLINK+="disk/zpool/g13"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:16-lun0", SYMLINK+="disk/zpool/g14"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*0:*:17-lun0", SYMLINK+="disk/zpool/g15"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:3-lun0", SYMLINK+="disk/zpool/h1"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:4-lun0", SYMLINK+="disk/zpool/h2"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:5-lun0", SYMLINK+="disk/zpool/h3"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:6-lun0", SYMLINK+="disk/zpool/h4"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:7-lun0", SYMLINK+="disk/zpool/h5"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:8-lun0", SYMLINK+="disk/zpool/h6"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:9-lun0", SYMLINK+="disk/zpool/h7"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:10-lun0", SYMLINK+="disk/zpool/h8"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:11-lun0", SYMLINK+="disk/zpool/h9"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:12-lun0", SYMLINK+="disk/zpool/h10"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:13-lun0", SYMLINK+="disk/zpool/h11"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:14-lun0", SYMLINK+="disk/zpool/h12"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:15-lun0", SYMLINK+="disk/zpool/h13"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:16-lun0", SYMLINK+="disk/zpool/h14"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:85:00.0*4:*:17-lun0", SYMLINK+="disk/zpool/h15"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:0-lun0", SYMLINK+="disk/zpool/i1"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:1-lun0", SYMLINK+="disk/zpool/i2"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:2-lun0", SYMLINK+="disk/zpool/i3"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:3-lun0", SYMLINK+="disk/zpool/i4"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:4-lun0", SYMLINK+="disk/zpool/i5"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:5-lun0", SYMLINK+="disk/zpool/i6"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:6-lun0", SYMLINK+="disk/zpool/i7"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:7-lun0", SYMLINK+="disk/zpool/i8"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:8-lun0", SYMLINK+="disk/zpool/i9"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:9-lun0", SYMLINK+="disk/zpool/i10"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:10-lun0", SYMLINK+="disk/zpool/i11"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:11-lun0", SYMLINK+="disk/zpool/i12"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:12-lun0", SYMLINK+="disk/zpool/i13"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:13-lun0", SYMLINK+="disk/zpool/i14"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:14-lun0", SYMLINK+="disk/zpool/i15"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*0:*:15-lun0", SYMLINK+="disk/zpool/i16"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:0-lun0", SYMLINK+="disk/zpool/j1"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:1-lun0", SYMLINK+="disk/zpool/j2"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:2-lun0", SYMLINK+="disk/zpool/j3"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:3-lun0", SYMLINK+="disk/zpool/j4"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:4-lun0", SYMLINK+="disk/zpool/j5"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:5-lun0", SYMLINK+="disk/zpool/j6"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:6-lun0", SYMLINK+="disk/zpool/j7"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:7-lun0", SYMLINK+="disk/zpool/j8"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:8-lun0", SYMLINK+="disk/zpool/j9"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:9-lun0", SYMLINK+="disk/zpool/j10"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:10-lun0", SYMLINK+="disk/zpool/j11"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:11-lun0", SYMLINK+="disk/zpool/j12"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:12-lun0", SYMLINK+="disk/zpool/j13"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:13-lun0", SYMLINK+="disk/zpool/j14"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:14-lun0", SYMLINK+="disk/zpool/j15"
ENV{DEVTYPE}=="disk", ENV{ID_PATH}=="*:83:00.0*4:*:15-lun0", SYMLINK+="disk/zpool/j16"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
# Partitions (*:pci*port:*:id-lun)
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:3-lun0", SYMLINK+="disk/zpool/a1-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:4-lun0", SYMLINK+="disk/zpool/a2-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:5-lun0", SYMLINK+="disk/zpool/a3-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:6-lun0", SYMLINK+="disk/zpool/a4-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:7-lun0", SYMLINK+="disk/zpool/a5-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:8-lun0", SYMLINK+="disk/zpool/a6-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:9-lun0", SYMLINK+="disk/zpool/a7-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:10-lun0", SYMLINK+="disk/zpool/a8-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:11-lun0", SYMLINK+="disk/zpool/a9-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:12-lun0", SYMLINK+="disk/zpool/a10-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:13-lun0", SYMLINK+="disk/zpool/a11-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:14-lun0", SYMLINK+="disk/zpool/a12-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:15-lun0", SYMLINK+="disk/zpool/a13-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:16-lun0", SYMLINK+="disk/zpool/a14-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*0:*:17-lun0", SYMLINK+="disk/zpool/a15-part%n"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:3-lun0", SYMLINK+="disk/zpool/b1-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:4-lun0", SYMLINK+="disk/zpool/b2-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:5-lun0", SYMLINK+="disk/zpool/b3-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:6-lun0", SYMLINK+="disk/zpool/b4-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:7-lun0", SYMLINK+="disk/zpool/b5-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:8-lun0", SYMLINK+="disk/zpool/b6-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:9-lun0", SYMLINK+="disk/zpool/b7-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:10-lun0", SYMLINK+="disk/zpool/b8-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:11-lun0", SYMLINK+="disk/zpool/b9-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:12-lun0", SYMLINK+="disk/zpool/b10-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:13-lun0", SYMLINK+="disk/zpool/b11-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:14-lun0", SYMLINK+="disk/zpool/b12-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:15-lun0", SYMLINK+="disk/zpool/b13-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:16-lun0", SYMLINK+="disk/zpool/b14-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:03:00.0*4:*:17-lun0", SYMLINK+="disk/zpool/b15-part%n"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:3-lun0", SYMLINK+="disk/zpool/c1-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:4-lun0", SYMLINK+="disk/zpool/c2-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:5-lun0", SYMLINK+="disk/zpool/c3-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:6-lun0", SYMLINK+="disk/zpool/c4-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:7-lun0", SYMLINK+="disk/zpool/c5-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:8-lun0", SYMLINK+="disk/zpool/c6-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:9-lun0", SYMLINK+="disk/zpool/c7-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:10-lun0", SYMLINK+="disk/zpool/c8-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:11-lun0", SYMLINK+="disk/zpool/c9-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:12-lun0", SYMLINK+="disk/zpool/c10-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:13-lun0", SYMLINK+="disk/zpool/c11-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:14-lun0", SYMLINK+="disk/zpool/c12-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:15-lun0", SYMLINK+="disk/zpool/c13-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:16-lun0", SYMLINK+="disk/zpool/c14-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*0:*:17-lun0", SYMLINK+="disk/zpool/c15-part%n"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:3-lun0", SYMLINK+="disk/zpool/d1-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:4-lun0", SYMLINK+="disk/zpool/d2-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:5-lun0", SYMLINK+="disk/zpool/d3-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:6-lun0", SYMLINK+="disk/zpool/d4-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:7-lun0", SYMLINK+="disk/zpool/d5-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:8-lun0", SYMLINK+="disk/zpool/d6-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:9-lun0", SYMLINK+="disk/zpool/d7-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:10-lun0", SYMLINK+="disk/zpool/d8-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:11-lun0", SYMLINK+="disk/zpool/d9-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:12-lun0", SYMLINK+="disk/zpool/d10-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:13-lun0", SYMLINK+="disk/zpool/d11-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:14-lun0", SYMLINK+="disk/zpool/d12-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:15-lun0", SYMLINK+="disk/zpool/d13-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:16-lun0", SYMLINK+="disk/zpool/d14-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:04:00.0*4:*:17-lun0", SYMLINK+="disk/zpool/d15-part%n"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:3-lun0", SYMLINK+="disk/zpool/e1-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:4-lun0", SYMLINK+="disk/zpool/e2-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:5-lun0", SYMLINK+="disk/zpool/e3-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:6-lun0", SYMLINK+="disk/zpool/e4-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:7-lun0", SYMLINK+="disk/zpool/e5-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:8-lun0", SYMLINK+="disk/zpool/e6-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:9-lun0", SYMLINK+="disk/zpool/e7-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:10-lun0", SYMLINK+="disk/zpool/e8-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:11-lun0", SYMLINK+="disk/zpool/e9-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:12-lun0", SYMLINK+="disk/zpool/e10-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:13-lun0", SYMLINK+="disk/zpool/e11-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:14-lun0", SYMLINK+="disk/zpool/e12-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:15-lun0", SYMLINK+="disk/zpool/e13-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:16-lun0", SYMLINK+="disk/zpool/e14-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*0:*:17-lun0", SYMLINK+="disk/zpool/e15-part%n"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:3-lun0", SYMLINK+="disk/zpool/f1-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:4-lun0", SYMLINK+="disk/zpool/f2-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:5-lun0", SYMLINK+="disk/zpool/f3-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:6-lun0", SYMLINK+="disk/zpool/f4-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:7-lun0", SYMLINK+="disk/zpool/f5-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:8-lun0", SYMLINK+="disk/zpool/f6-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:9-lun0", SYMLINK+="disk/zpool/f7-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:10-lun0", SYMLINK+="disk/zpool/f8-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:11-lun0", SYMLINK+="disk/zpool/f9-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:12-lun0", SYMLINK+="disk/zpool/f10-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:13-lun0", SYMLINK+="disk/zpool/f11-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:14-lun0", SYMLINK+="disk/zpool/f12-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:15-lun0", SYMLINK+="disk/zpool/f13-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:16-lun0", SYMLINK+="disk/zpool/f14-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:84:00.0*4:*:17-lun0", SYMLINK+="disk/zpool/f15-part%n"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:3-lun0", SYMLINK+="disk/zpool/g1-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:4-lun0", SYMLINK+="disk/zpool/g2-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:5-lun0", SYMLINK+="disk/zpool/g3-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:6-lun0", SYMLINK+="disk/zpool/g4-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:7-lun0", SYMLINK+="disk/zpool/g5-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:8-lun0", SYMLINK+="disk/zpool/g6-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:9-lun0", SYMLINK+="disk/zpool/g7-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:10-lun0", SYMLINK+="disk/zpool/g8-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:11-lun0", SYMLINK+="disk/zpool/g9-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:12-lun0", SYMLINK+="disk/zpool/g10-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:13-lun0", SYMLINK+="disk/zpool/g11-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:14-lun0", SYMLINK+="disk/zpool/g12-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:15-lun0", SYMLINK+="disk/zpool/g13-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:16-lun0", SYMLINK+="disk/zpool/g14-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*0:*:17-lun0", SYMLINK+="disk/zpool/g15-part%n"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:3-lun0", SYMLINK+="disk/zpool/h1-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:4-lun0", SYMLINK+="disk/zpool/h2-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:5-lun0", SYMLINK+="disk/zpool/h3-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:6-lun0", SYMLINK+="disk/zpool/h4-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:7-lun0", SYMLINK+="disk/zpool/h5-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:8-lun0", SYMLINK+="disk/zpool/h6-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:9-lun0", SYMLINK+="disk/zpool/h7-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:10-lun0", SYMLINK+="disk/zpool/h8-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:11-lun0", SYMLINK+="disk/zpool/h9-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:12-lun0", SYMLINK+="disk/zpool/h10-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:13-lun0", SYMLINK+="disk/zpool/h11-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:14-lun0", SYMLINK+="disk/zpool/h12-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:15-lun0", SYMLINK+="disk/zpool/h13-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:16-lun0", SYMLINK+="disk/zpool/h14-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:85:00.0*4:*:17-lun0", SYMLINK+="disk/zpool/h15-part%n"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:0-lun0", SYMLINK+="disk/zpool/i1-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:1-lun0", SYMLINK+="disk/zpool/i2-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:2-lun0", SYMLINK+="disk/zpool/i3-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:3-lun0", SYMLINK+="disk/zpool/i4-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:4-lun0", SYMLINK+="disk/zpool/i5-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:5-lun0", SYMLINK+="disk/zpool/i6-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:6-lun0", SYMLINK+="disk/zpool/i7-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:7-lun0", SYMLINK+="disk/zpool/i8-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:8-lun0", SYMLINK+="disk/zpool/i9-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:9-lun0", SYMLINK+="disk/zpool/i10-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:10-lun0", SYMLINK+="disk/zpool/i11-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:11-lun0", SYMLINK+="disk/zpool/i12-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:12-lun0", SYMLINK+="disk/zpool/i13-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:13-lun0", SYMLINK+="disk/zpool/i14-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:14-lun0", SYMLINK+="disk/zpool/i15-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*0:*:15-lun0", SYMLINK+="disk/zpool/i16-part%n"
Update zpool-configs to be udev aware. To simplify creation and management of test configurations the dragon and x4550 configureis have been integrated with udev. Our current best guess as to how we'll actually manage the disks in these systems is with a udev mapping scheme. The current leading scheme is to map each drive to a simpe <CHANNEL><RANK> id. In this mapping each CHANNEL is represented by the letters a-z, and the RANK is represented by the numbers 1-n. A CHANNEL should identify a group of RANKS which are all attached to a single controller, each RANK represents a disk. This provides a nice mechanism to locate a specific drive given a known hardware configuration. Various hardware vendors use a similar scheme. A nice side effect of these changes is it allowed me to make the raid0/raid10/raidz/raidz2 setup functions generic. This makes adding new test configs easy, you just need to create a udev rules file for your test config which conforms to the naming scheme.
2009-10-21 18:38:51 +00:00
Udev rule was a little to broad include the -lun0 in the pattern.
2009-10-23 18:49:08 +00:00
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:0-lun0", SYMLINK+="disk/zpool/j1-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:1-lun0", SYMLINK+="disk/zpool/j2-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:2-lun0", SYMLINK+="disk/zpool/j3-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:3-lun0", SYMLINK+="disk/zpool/j4-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:4-lun0", SYMLINK+="disk/zpool/j5-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:5-lun0", SYMLINK+="disk/zpool/j6-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:6-lun0", SYMLINK+="disk/zpool/j7-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:7-lun0", SYMLINK+="disk/zpool/j8-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:8-lun0", SYMLINK+="disk/zpool/j9-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:9-lun0", SYMLINK+="disk/zpool/j10-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:10-lun0", SYMLINK+="disk/zpool/j11-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:11-lun0", SYMLINK+="disk/zpool/j12-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:12-lun0", SYMLINK+="disk/zpool/j13-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:13-lun0", SYMLINK+="disk/zpool/j14-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:14-lun0", SYMLINK+="disk/zpool/j15-part%n"
ENV{DEVTYPE}=="partition", ENV{ID_PATH}=="*:83:00.0*4:*:15-lun0", SYMLINK+="disk/zpool/j16-part%n"