Debian, LVM, udev, IDS
Posted in 2011
Topics: Storage & Space Management, Versions, Editions & End-of-Life
Old box: Ubuntu Hardy, LVM, IDS 7.3 (I said old) Script in /etc/init.d to set ownership & permissions - informix,informix,660 - before starting IDS. No problem. New box: Debian Squeeze, LVM, IDS 11.7 Same script. Check device permissions set as required. Try to initialise new root chunk. IDS complains that the owner & root should be informix. Check again & it's now set to root. My suspicion is that udev is butting in so I removed the script & tried to set up udev permissions as per example at http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/LVM2/udev/12-dm-permissions.rules?rev=1.6&content-type=text/plain&cvsroot=lvm2 which in turn is as advised at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606124 Result: everything's still owned by root. Has anyone got this combination working and if so how? -- Ian The Hotmail address is my spam-bin. Real mail address is iang at austonley org uk
Ian Goddard wrote: > Old box: > > Ubuntu Hardy, LVM, IDS 7.3 (I said old) > Script in /etc/init.d to set ownership & permissions - > informix,informix,660 - before starting IDS. No problem. > > New box: > Debian Squeeze, LVM, IDS 11.7 > Same script. Check device permissions set as required. Try to initialise > new root chunk. IDS complains that the owner & root should be informix. > Check again & it's now set to root. > > My suspicion is that udev is butting in so I removed the script & tried > to set up udev permissions as per example at > http://sourceware.org/cgi-bin/cvsweb.cgi/~checkout~/LVM2/udev/12-dm-permissions.rules?rev=1.6&content-type=text/plain&cvsroot=lvm2 > which in turn is as advised at > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606124 > > Result: everything's still owned by root. > > Has anyone got this combination working and if so how? > > The example at sourceware gives a a set of sample lines form LVM devices. The example for a named logical volume is ENV{DM_VG_NAME}=="VolGroup00", ENV{DM_LV_NAME}=="LogVol00", OWNER:="root", GROUP:="root", MODE:="660" In my case the volume group name is vg and the entry in /dev/mapper is of the form vg-lv_inf_root so I put these strings into the example in place of the VolGroup00 and LogVol00 respectively - with informix as owner & group of course: ENV{DM_VG_NAME}=="vg", ENV{DM_LV_NAME}=="vg-lv_inf_root", OWNER:="root", GROUP:="root", MODE:="660" This is wrong. The actual volume name, as defined to lvm is lv_informix_root without the volume group name prepended and this is what should be used in the permissions file: ENV{DM_VG_NAME}=="vg", ENV{DM_LV_NAME}=="lv_inf_root", OWNER:="root", GROUP:="root", MODE:="660" This and similar lines for as many chunk devices as are required go into a file /etc/udev/rules.d/99-informix-permissions Once these are in place the ownership and permissions are set correctly at boot time and remain set when the instance is initialised. I haven't set the databases up yet but so far, so good. There is, BTW, an alternative line that works, bases on the sample for a plain dynamically mapped device: ENV{DM_NAME}=="vg-lv_inf_root", OWNER:="root", GROUP:="root", MODE:="660" This does use the full name as found in /dev/mapper. You pays your money and you takes your choice. -- Ian The Hotmail address is my spam-bin. Real mail address is iang at austonley org uk