Raw Devices on Suse Linux 11.3, IDS 11.50.FC5TL

Hi there, with Suse 11.2 and IDS 11.50.FC5TL i had so far no problems, but after installing Suse 11.3 i got some problems with my raw devices and installation. 1. "oninit -ivy" AND "oninit -v" cannot be done without "KAIOOFF=1". If you start without "KAIOOFF=1", IDS sends numerous error messages and "oninit -ivy" ends in a panic server crash, while "oninit -v" makes the system going well but some dbspaces will be marked as "down" because they have not the appropriate owner/group: 18:36:20 The chunk '/db/inf/dev/stieff/temp1_001' must have owner-ID "informix" and group-ID "informix". 18:36:20 The chunk '/db/inf/dev/stieff/temp3_001' must have owner-ID "informix" and group-ID "informix". Another Dbspace (a temporary smart blob space) is also be marked as "Down" but it seems, that the permissions (and owner/group) are ok. 2. To avoid the errors described under 1. i start IDS with the following procedure: # Informix Startdatei chown informix:informix /dev/dm* # necessary, because onmode -ky changes owner and group!!! su - informix -c "export KAIOOFF=1; nohup oninit -v" & for (( i=1; i <= 20 ; i++ )) do chown informix:informix /dev/dm* sleep 1 done Every time i stop IDS (onmode -ky) the raw devices have suddenly owner=root and group=disk. So i added the statement "chown informix:informix /dev/dm*" in my start-routine, but this won't do, because IDS changes directly after the starting the owner/group of all Raw devices to "root/disk". To avoid the error messages mentioned above i added this little loop "for (( i=1....... " and then there are no error messages in the message log file. 3. In Suse 11.2 logical volumes (which i use as raw devices) are linked to /dev/system/inf_0_001 -> /dev/mapper/system-inf_0_001 Owner/group of /dev/mapper/system-xxxx will NOT be changed by the oninit process. In Suse 11.3, logical volumes (which i use as raw devices) are linked to /dev/system/inf_0_001 -> ../dm-0 All Blockdevices for the logical volumes are now in the directory /dev: /dev/dm-0, /dev/dm-1 and so on. I don't know whether this change is responsible for the problems described in Point 1. and 2. 4. Every time oninit is started it gives the following message: 19:00:27 IBM Informix Dynamic Server Started. Thu Jul 29 19:00:29 2010 19:00:29 pid 8305: can't get real path of # <---------------------------------------------------------- Does anyone here know what this means "can't get real path of "? Is it perhaps the Link " /dev/system/inf_0_001 -> ../dm-0" ??? The Links to my chunks looks like this: 600171c0 1 1 0 100000 78565 PO-BD /db/inf/dev/stieff/inf_0_001 # <---- Root Dbspace 61164688 2 2 0 256000 5947 PO-BD /db/inf/dev/stieff/physdbs_001 61164878 3 3 0 1048576 23523 PO-BD /db/inf/dev/stieff/logdbs_001 61164a68 4 4 0 2560000 2558593 PO-BD /db/inf/dev/stieff/daten1_001 And these symbolic Links are attached to the correct Blockdevices: 107 lrwxrwxrwx 1 root informix 9 24. Jul 18:49 /db/inf/dev/stieff/daten1_001 -> /dev/dm-3 108 lrwxrwxrwx 1 root informix 9 24. Jul 18:50 /db/inf/dev/stieff/daten1_002 -> /dev/dm-4 104 lrwxrwxrwx 1 root informix 9 23. Jul 18:05 /db/inf/dev/stieff/inf_0_001 -> /dev/dm-0 106 lrwxrwxrwx 1 root informix 9 24. Jul 18:49 /db/inf/dev/stieff/logdbs_001 -> /dev/dm-2 105 lrwxrwxrwx 1 root informix 9 24. Jul 18:48 /db/inf/dev/stieff/physdbs_001 -> /dev/dm-1 Owner/Group of /dev/dm-* are correct: 3868 brw-rw---- 1 informix informix 253, 0 29. Jul 20:16 /dev/dm-0 3910 brw-rw---- 1 informix informix 253, 1 29. Jul 20:16 /dev/dm-1 3944 brw-rw---- 1 informix informix 253, 2 29. Jul 20:16 /dev/dm-2 3978 brw-rw---- 1 informix informix 253, 3 29. Jul 19:00 /dev/dm-3 4012 brw-rw---- 1 informix informix 253, 4 29. Jul 19:00 /dev/dm-4 .... I hope that in this discussion-list are some "Suse/Linux-Expert", who could help me. Thanks Christian Winterhager

Is that on openSUSE or SLES? Jonathon Wyza CX & CBORD System Administrator CX Programmer/Analyst Administrative Computing Bethel College (574)-257-3381 AIM: Iamwyza jonathon.wyza@bethelcollege.edu ============================== SLES 11x64 & IDS 11.50.FC6 "Don't document the problem, fix it." - Atli Björgvin Oddsson -----Original Message----- From: ids-bounces@iiug.org [mailto:ids-bounces@iiug.org] On Behalf Of Christian Winterhager Sent: Thursday, July 29, 2010 2:41 PM To: ids@iiug.org Subject: Raw Devices on Suse Linux 11.3, IDS 11.50.FC5TL [20695] Hi there, with Suse 11.2 and IDS 11.50.FC5TL i had so far no problems, but after installing Suse 11.3 i got some problems with my raw devices and installation. 1. "oninit -ivy" AND "oninit -v" cannot be done without "KAIOOFF=1". If you start without "KAIOOFF=1", IDS sends numerous error messages and "oninit -ivy" ends in a panic server crash, while "oninit -v" makes the system going well but some dbspaces will be marked as "down" because they have not the appropriate owner/group: 18:36:20 The chunk '/db/inf/dev/stieff/temp1_001' must have owner-ID "informix" and group-ID "informix". 18:36:20 The chunk '/db/inf/dev/stieff/temp3_001' must have owner-ID "informix" and group-ID "informix". Another Dbspace (a temporary smart blob space) is also be marked as "Down" but it seems, that the permissions (and owner/group) are ok. 2. To avoid the errors described under 1. i start IDS with the following procedure: # Informix Startdatei chown informix:informix /dev/dm* # necessary, because onmode -ky changes owner and group!!! su - informix -c "export KAIOOFF=1; nohup oninit -v" & for (( i=1; i <= 20 ; i++ )) do chown informix:informix /dev/dm* sleep 1 done Every time i stop IDS (onmode -ky) the raw devices have suddenly owner=root and group=disk. So i added the statement "chown informix:informix /dev/dm*" in my start-routine, but this won't do, because IDS changes directly after the starting the owner/group of all Raw devices to "root/disk". To avoid the error messages mentioned above i added this little loop "for (( i=1....... " and then there are no error messages in the message log file. 3. In Suse 11.2 logical volumes (which i use as raw devices) are linked to /dev/system/inf_0_001 -> /dev/mapper/system-inf_0_001 Owner/group of /dev/mapper/system-xxxx will NOT be changed by the oninit process. In Suse 11.3, logical volumes (which i use as raw devices) are linked to /dev/system/inf_0_001 -> ../dm-0 All Blockdevices for the logical volumes are now in the directory /dev: /dev/dm-0, /dev/dm-1 and so on. I don't know whether this change is responsible for the problems described in Point 1. and 2. 4. Every time oninit is started it gives the following message: 19:00:27 IBM Informix Dynamic Server Started. Thu Jul 29 19:00:29 2010 19:00:29 pid 8305: can't get real path of # <---------------------------------------------------------- Does anyone here know what this means "can't get real path of "? Is it perhaps the Link " /dev/system/inf_0_001 -> ../dm-0" ??? The Links to my chunks looks like this: 600171c0 1 1 0 100000 78565 PO-BD /db/inf/dev/stieff/inf_0_001 # <---- Root Dbspace 61164688 2 2 0 256000 5947 PO-BD /db/inf/dev/stieff/physdbs_001 61164878 3 3 0 1048576 23523 PO-BD /db/inf/dev/stieff/logdbs_001 61164a68 4 4 0 2560000 2558593 PO-BD /db/inf/dev/stieff/daten1_001 And these symbolic Links are attached to the correct Blockdevices: 107 lrwxrwxrwx 1 root informix 9 24. Jul 18:49 /db/inf/dev/stieff/daten1_001 -> /dev/dm-3 108 lrwxrwxrwx 1 root informix 9 24. Jul 18:50 /db/inf/dev/stieff/daten1_002 -> /dev/dm-4 104 lrwxrwxrwx 1 root informix 9 23. Jul 18:05 /db/inf/dev/stieff/inf_0_001 -> /dev/dm-0 106 lrwxrwxrwx 1 root informix 9 24. Jul 18:49 /db/inf/dev/stieff/logdbs_001 -> /dev/dm-2 105 lrwxrwxrwx 1 root informix 9 24. Jul 18:48 /db/inf/dev/stieff/physdbs_001 -> /dev/dm-1 Owner/Group of /dev/dm-* are correct: 3868 brw-rw---- 1 informix informix 253, 0 29. Jul 20:16 /dev/dm-0 3910 brw-rw---- 1 informix informix 253, 1 29. Jul 20:16 /dev/dm-1 3944 brw-rw---- 1 informix informix 253, 2 29. Jul 20:16 /dev/dm-2 3978 brw-rw---- 1 informix informix 253, 3 29. Jul 19:00 /dev/dm-3 4012 brw-rw---- 1 informix informix 253, 4 29. Jul 19:00 /dev/dm-4 ..... I hope that in this discussion-list are some "Suse/Linux-Expert", who could help me. Thanks Christian Winterhager ******************************************************************************* Forum Note: Use "Reply" to post a response in the discussion forum.

Am 29.07.2010 20:44, schrieb Wyza, Jonathon: > Is that on openSUSE or SLES? > > It is OpenSUSE 11.3