Raw disk device setup in Suse Linux 9
Problem: on SuSE Linux 9, raw device bindings and ownership/permissions for Informix chunks didn't survive a reboot, unlike Red Hat AS 2.1's /etc/sysconfig/rawdevices; udev.permissions settings were also ignored, forcing manual chown/chgrp/chmod. Replies pointed to SuSE's /etc/raw file (see 'man raw') for persistent raw-to-block bindings, one poster said he only fixed permissions by editing the init.d script, and another reported success using hard links (not symlinks) in a separate directory with friendly names, setting ownership on those links and referencing them in the Informix configuration. No single definitive fix is agreed on.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
In Red Hat Advanvced Server 2.1, setting up raw disk devices was rather straightforward - primarily, you defined the mapping in the /etc/sysconfig/rawdevices file and the configuration was saved. In Suse Linux version 9, we are trying to do the same thing, however the documentation does not seem to indicate how exactly to configure raw devices so that the configuration is saved. We went through the documentation and we were able to successfully configure them the way we wanted (although we ran into several glitches such the udev.permissions file not following the owner/group/permission info we setup there per the documentation - we had to go in and do the old fashioned chown/chgrp/chmod), however once the machine was rebooted, the configuration was "lost". Any input or pointing me in the right direction would be appreciated. Hal Maner
On the SuSE 9.1 Professional release there is a /etc/raw file, but I don't have SLES9 in front of me to tell you what it does differently. This file is pretty straightforward as well. # /etc/raw # # sample configuration to bind raw devices # to block devices # # The format of this file is: # raw<N>:<blockdev> # # example: # --------- # raw1:hdb1 # # this means: bind /dev/raw/raw1 to /dev/hdb1 # # ... Run "man raw" for more information. "raw" is a command from Red Hat, so should be basically the same implementation as on Red Hat. -DG- Hal Maner wrote: > In Red Hat Advanvced Server 2.1, setting up raw disk devices was rather > straightforward - primarily, you defined the mapping in the > /etc/sysconfig/rawdevices file and the configuration was saved. > > In Suse Linux version 9, we are trying to do the same thing, however the > documentation does not seem to indicate how exactly to configure raw devices > so that the configuration is saved. We went through the documentation and > we were able to successfully configure them the way we wanted (although we > ran into several glitches such the udev.permissions file not following the > owner/group/permission info we setup there per the documentation - we had to > go in and do the old fashioned chown/chgrp/chmod), however once the machine > was rebooted, the configuration was "lost". > > Any input or pointing me in the right direction would be appreciated. > > Hal Maner > > >
Had exactly the same, and never resolved it except by changing the permissions in the init.d script. See my private post for more details. regards -- Neil Truby t:01932 724027 Director m:07798 811708 Ardenta Limited e:neil.truby@ardenta.com "Hal Maner" <hmaner@msystemsintlnospam.com> wrote in message news:0Z7ed.4458$5i5.1690@newsread2.news.atl.earthlink.net... > In Red Hat Advanvced Server 2.1, setting up raw disk devices was rather > straightforward - primarily, you defined the mapping in the > /etc/sysconfig/rawdevices file and the configuration was saved. > > In Suse Linux version 9, we are trying to do the same thing, however the > documentation does not seem to indicate how exactly to configure raw > devices > so that the configuration is saved. We went through the documentation and > we were able to successfully configure them the way we wanted (although we > ran into several glitches such the udev.permissions file not following the > owner/group/permission info we setup there per the documentation - we had > to > go in and do the old fashioned chown/chgrp/chmod), however once the > machine > was rebooted, the configuration was "lost". > > Any input or pointing me in the right direction would be appreciated. > > Hal Maner > > >
"Hal Maner" <hmaner@msystemsintlnospam.com> schrieb im Newsbeitrag news:0Z7ed.4458$5i5.1690@newsread2.news.atl.earthlink.net... > In Red Hat Advanvced Server 2.1, setting up raw disk devices was rather > straightforward - primarily, you defined the mapping in the > /etc/sysconfig/rawdevices file and the configuration was saved. > > In Suse Linux version 9, we are trying to do the same thing, however the > documentation does not seem to indicate how exactly to configure raw devices > so that the configuration is saved. We went through the documentation and > we were able to successfully configure them the way we wanted (although we > ran into several glitches such the udev.permissions file not following the > owner/group/permission info we setup there per the documentation - we had to > go in and do the old fashioned chown/chgrp/chmod), however once the machine > was rebooted, the configuration was "lost". > > Any input or pointing me in the right direction would be appreciated. > > Hal Maner > > We solved it a little bit in a other way: We created several links in a other directory ( ln /dev/rawharddisc /DBS/datastore ) to the raw devices. We then changed permissions, users and groups only on the new created links and used the links during the On-Line configuration. This way had nice options: -no hassle with (re)setting the permissions deep in the system -a very "speaking" name on the raw devices during configuration -we don't need to seek a list of several dozen device names under /dev.... I hope my suggestion helps. Joerg
"Joerg Volz" <joerg@microplus.de> wrote in message news:417933a8$2@news.punkt.de... > We solved it a little bit in a other way: > > We created several links in a other directory ( ln /dev/rawharddisc > /DBS/datastore ) to the raw devices. > We then changed permissions, users and groups only on the new created > links > and used the links during the On-Line configuration. > > This way had nice options: > > -no hassle with (re)setting the permissions deep in the system > -a very "speaking" name on the raw devices during configuration > -we don't need to seek a list of several dozen device names under /dev.... > > I hope my suggestion helps. > > Joerg > > > It didn't help me as I recall, because I used links too (/opt/informix/dbspaces2/rootdbs -> /dev/raw.....) , but it is immaterial what permission the links have, if the devices' permissions are altered Informix won't start. But perhaps I misunderstood what you said? Or perhaps - as your post suggests - you used hard links and this makes a difference ... -- Neil Truby t:01932 724027 Director m:07798 811708 Ardenta Limited e:neil.truby@ardenta.com
"Neil Truby" <neil.truby@ardenta.com> schrieb im Newsbeitrag news:2tsqmrF2314hhU1@uni-berlin.de... > > > It didn't help me as I recall, because I used links too > (/opt/informix/dbspaces2/rootdbs -> /dev/raw.....) , but it is immaterial > what permission the links have, if the devices' permissions are altered > Informix won't start. But perhaps I misunderstood what you said? Or > perhaps - as your post suggests - you used hard links and this makes a > difference ... > As you say, we used hard links. Sorry, I forgot to tell you. Joerg