On Thu, Apr 16, 2009 at 2:24 AM, Sharpe, Sam J <[email protected]> wrote: > 2009/4/16 Vanco Backup <[email protected]>: >> I'm setting up a RHEL5U3 host to support Oracle RAC. The customer >> still uses raw devices. In one case there are 9 raw devices, in >> another 17. > <snip> >> I create a rules file for permissions - >> /etc/udev/rules.d/99-raw-permissions.rules >> >> On the host with only 9 raw devices, a "wildcarded" ruleS work just fine - >> e.g.: >> >> KERNEL=="raw[0-2]", OWNER="oracle", GROUP="oinstall", MODE="640" >> KERNEL=="raw[5-7]", OWNER="oracle", GROUP="dba", MODE="660" >> KERNEL=="raw[8-9]", OWNER="root", GROUP="oinstall", MODE="640" >> >> However - on the hosts with > 9 raw devices, the permissions fail to >> get applied, e.g.: >> KERNEL=="raw[10-17]", OWNER="root", GROUP="oinstall", MODE="640" > > Have you tried KERNEL=="raw1[0-7]", OWNER="root" GROUP="oinstall", MODE="640" > > Because my first thought was that udev is not expanding [10-17] > properly as it's the only apparent difference between the first set of > rules and this.
Ah, actually that makes good sense. I bet that works. On a related note - can anyone offer comment on adding a perms rule for the sym link? In other words, for my device I define as follows: ACTION=="add", KERNEL=="sd*[!0-9]", PROGRAM=="/sbin/scsi_id -g -u -s %p", RESULT=="3<snip>", RUN+="/bin/raw /dev/raw/raw1 %N" SYMLINK+="asm1" ...can I just duplicate the rule I made for the raw device for the sym-linked device? I'm a bit wary of "testing" theory as these are customer servers..... _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
