Technical article 126802

How to configure and use ODM for disk mirroring Raid 1 under SCO OpenServer 6?

OpenServer 6.0.0

Written · Last revised

Problem

How can I configure and administrate ODM under SCO OpenServer 6.0.0 for disk mirroring (Raid 1) only?

Also, what to do in case of a failed disk in the ODM mirror?

NOTE:
          Note 1:

Before you start, make sure you have the following:

- In our example, we are going to configure a mirror set (Raid 1) ONLY, as this is what is needed.

Therefore, you only need to obtain the SCO OpenServer 6 Disk Mirroring License.

For configuring RAID 0, 1, 5 & 10, you need to obtain the full SCO OpenServer 6 Online Data Manager License.

This is explained in a separate TA126803.

- SCO OpenServer 6.0.0 MP3 installed.

- SCO VERITAS Online Disk Manager (ODM) ver 3.2Aa installed.

Please Note: If ODM was installed after MP3, then no need to re-install the whole of MP3 in order to install the ODM fixes. You only need to choose the ODM fix when using "custom" to install MP3.

- Your "scologin X-session" is working.
Note 2:

You need to be aware of the following info, which will help you to understand how ODM Mirroring works.

ODM Mirroring does not mirror the whole physical disk to the other, like in a hardware mirror. But it only mirrors the filesystems on the disks.

So VxFS filesystems needs to be first configured on a disk via ODM and then mirror these filesystems across to the other disk.

On our example system, we have three disks:

# sdiconfig -l
0:0,7,0: HBA     : (mpt,1)LSI Logic 1030 10414
  0,0,0: DISK    : FUJITSU MAS3184NC       5205
  0,1,0: DISK    : MAXTOR  ATLASU320_36_SCAB434
  0,2,0: DISK    : MAXTOR  ATLASU320_36_SCAB434
  0,6,0: TAPE    : SONY    SDT-10000       01u1
  0,8,0: HBA     : SDR     GEM318          0
1:0,2,0: HBA     : (ide,1) Generic IDE/ATAPI
  0,0,0: CDROM   : HL-DT-STDVD-ROM GDR8163B0F15

Disk1 - 18 GB, FUJITSU MAS3184NC will be used only for the SCO OpenServer6 installation (boot disk).

Disk-2&3 - 36 GB MAXTOR  ATLASU320_36_SCAB434 will be used as
critical data disk and will be mirrored (Raid 1) via ODM.
It is not recommended to encapsulate the root disk with ODM unless
there is a specific need and has been tested thoroughly.  This
generally fails because the SCSI controller in use is not able to
boot from the second disk or there is no vtoc written to the disk
first prior to ODM's installation.

Solution

In our example, we are going to leave disk1 alone and not allow ODM to control it.

This disk will host the OSR6 installation (Boot disk).

The other two 36 GB HD, will be used under ODM control as mirrored (Raid 1) disks.

Setting UP a Mirror
-------------------
As root, perform the following steps:
1-

You need first to initialize the two HD's that will be used under ODM by running "mkdev hd":

# mkdev hd

Mass storage devices are recognized automatically when the system is booted with a new device present.

Current hard disk configuration:
Alias    - Address  - Inquiry String
--------   --------   --------------
hba1     - c0b0t7   - (mpt,1)LSI Logic 1030 10414
disk1    - c0b0t0l0 - FUJITSU MAS3184NC       5205
disk2    - c0b0t1l0 - MAXTOR  ATLASU320_36_SCAB434
disk3    - c0b0t2l0 - MAXTOR  ATLASU320_36_SCAB434

Please enter the alias of the disk you wish to initialize ( type quit to exit ): <disk2>

Note: do not type <disk1>, as this is your boot disk.

If your disk was brand new and formatted then you will get this screen:

The recommended default partitioning for your disk
is:
a 100% "UNIX System" partition.

To select this, please type "y". To partition your disk differently, type "n" and the "fdisk" program will let you select other partitions. y

There are 35907743 blocks available in the UNIX area. Please enter the number of file systems you want this area to be divided into, or press <Return> to get the default of 7 file system(s) <0>

Here type "1"

The layout of the filesystems and swap area is now prepared.

Do you wish to make any manual adjustments to the sizes or names of the filesystems or swap area before they are created on the hard disk? (y/n) <y>

you end up with the divvy table with 1 divisions with names d00110 or similar. Do (enter) the following there:

"p" to Prevent a new file system from being created
    on this division. (We do not want a filesystem
    to be created).
"0" For Division the first division.
"q" to quit and then

"i" for Install (Install the division set-up shown).

This will prevent any divisions to be created on the disks.

As these disks will be under ODM control, no need to create OpenServer6 divisions on them.

You will then land back in the "mkdev hd" utility menu again.

If your disk was not brand new and had some other data on it (another partion), then you will get additional messages that needs answers. In our example the third disk had UnixWare7 partition on it:

Alias    - Address  - Inquiry String
--------   --------   --------------
hba1     - c0b0t7   - (mpt,1)LSI Logic 1030 10414
disk1    - c0b0t0l0 - FUJITSU MAS3184NC       5205
disk2    - c0b0t1l0 - MAXTOR  ATLASU320_36_SCAB434
disk3    - c0b0t2l0 - MAXTOR  ATLASU320_36_SCAB434

Please enter the alias of the disk you wish to initialize ( type quit to exit ): <disk3>

You will then enter the OSR6 partition utility (fdisk). choose the following option in the order:

- Option 3, delete them. - Option 1, create a Unix Partition (use 100% for Unix) - Option 4, Exit and update the disk configuration.

Next screen

You have chosen a hard disk partition that was last administered on a UnixWare system. The division layout of this hard disk partition cannot be changed, using SCO OpenServer 6 tools, if you wish to preserve the existing data on this disk partition.

You have two options.

If you wish to access data that is already on this disk, you should simply exit this tool and use the Scoadmin Filesystem Manager to update /etc/default/filesys.

If you wish to just create new filesystems on this disk partition, permanently discarding any data already on this disk partition, you should continue using this tool.

Type quit to exit this tool or create to proceed: <create>

Here type "create"

WARNING: You are about to permanently destroy the data contained in this disk partition.

Are you sure you wish to proceed?

Type quit to exit this tool or destroy to proceed: <destroy>

Here type "destroy"

Then you will enter the OSR6 division table information as above for disk2 and follow the same procedure.

Then quit the "mkdev hd" utility.

You are now ready to start the ODM configuration.

Note: If you fail to follow the above procedure in step 1, ODM will fail with the initialization setup.

2-

As root, run from the command line:

# vxinstall
you will get the following screen:
Volume Manager Installation
Menu: VolumeManager/Install

The Volume Manager names disks on your system using the controller and disk number of the disk, substituting them into the following pattern:

c<controller>b<bus>t<target>d<disk>
Some examples would be:

c0b0t0d0 - first controller, bus 0, first target, first disk c1b0t0d0 - second controller, bus 0, first target, first disk c1b0t1d0 - second controller, bus 0, second target, first disk

The Volume Manager has detected the following controllers on your system:

c0:
Hit RETURN to continue. <RETURN>

since in our example, we only have one disk controller, ODM displayed "c0", first disk controller with Valid HD

Next screen:
Volume Manager Installation
Menu: VolumeManager/Install

You will now be asked if you wish to use Quick Installation or Custom Installation. Custom Installation allows you to select how the Volume Manager will handle the installation of each disk attached to your system.

Quick Installation examines each disk attached to your system and attempts to create volumes to cover all disk partitions that might be used for file systems or for other similar purposes.

If you do not wish to use some disks with the Volume Manager, or if you wish to reinitialize some disks, use the Custom Installation option Otherwise, we suggest that you use the Quick Installation option.

Hit RETURN to continue. <RETURN>
Next screen:
Volume Manager Installation Options
Menu: VolumeManager/Install
1      Quick Installation
2      Custom Installation
?      Display help about menu
??     Display help about the menuing system
q      Exit from menus
Select an operation to perform:

We will choose "2 - custom Installation", as we want to control which disks are to be configured under ODM for mirroring.

Note: With custom, we will leave the boot/root disk alone.

Next screen:
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom

The c0b0t0d0 disk is your Boot Disk. You can not add it as a new disk. If you encapsulate it, you will make your root filesystem and other system areas on the Boot Disk into volumes. This is required if you wish to mirror your root filesystem or system swap area.

Encapsulate Boot Disk [y,n,q,?] (default: n) <RETURN>
Next screen:

Volume Manager Custom Installation Menu: VolumeManager/Install/Custom/c0 Generating list of attached disks on c0....

<excluding root disk c0b0t0d0>

The Volume Manager has detected the following disks on controller c0:

c0b0t1d0 c0b0t2d0
Hit RETURN to continue. <RETURN>
Next screen:
Installation options for controller c0
Menu: VolumeManager/Install/Custom/c0
1  Install all disks as pre-existing disks.
   (encapsulate)
2  Install all disks as new disks. (discards data on
   disks!)
3  Install one disk at a time.
4  Leave these disks alone.
?  Display help about menu
?? Display help about the menuing system
q  Exit from menus
Select an operation to perform: <2>

Choose 2, install all disks as new disks.

Next screen:
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom/c0/Init

Use default disk names for these disks? [y,n,q,?] (default: y) <RETURN>

choose the default

The c0b0t1d0 disk will be given disk name disk01

Next screen:
Perform surface analysis (highly recommended)
[y,n,q,?] (default: y) <n>

PLEASE CHOOSE "n" and ignore the recommended, as this will take ages to finish. Not really needed for SCSI HDs.

do the same for disk02.
Next screen:
Volume Manager Custom Installation
Menu: VolumeManager/Install/Custom

The following is a summary of your choices.

c0b0t1d0        New Disk
c0b0t2d0        New Disk
Is this correct [y,n,q,?] (default: y) <RETURN>
Choose the default.
Next screen:
The Volume Manager is now reconfiguring (partition
phase)...

Volume Manager: Partitioning c0b0t1d0 as a new disk.

Volume Manager: Partitioning c0b0t2d0 as a new disk.

The Volume Manager is now reconfiguring (initialization
phase)...

Volume Manager: Adding disk01 (c0b0t1d0) as a new disk.

The Volume Daemon has been enabled for transactions.

Volume Manager: Adding disk02 (c0b0t2d0) as a new disk.

The system now must be shut down and rebooted in order to continue the reconfiguration.

Shutdown and reboot now [y,n,q,?] (default: n) <y>

Choose "y" for the server to reboot.

3-

After reboot to check that "xvinstall" was successful, run the following command as root:

# vxdiskadm

Type "list" or "l" to choose the "List disk information" then RETURN to choose the default "all"

you will see this output:
DEVICE       DISK         GROUP        STATUS
c0b0t0d0     -            -            error
c0b0t1d0     disk01       rootdg       online
c0b0t2d0     disk02       rootdg       online

Do not get worried about the "error" status of the Device c0b0t0d0, as this is our root boot disk and we did not want ODM to have control of it. this is why ODM if flagging it as status error, because it can't use it.

The other devices, c0b0t1d0 (disk01) & c0b0t2d0 (disk02) are flagged as status "online", which is good.

OR run the "vxprint" from the command line:

# vxprint
you will see this output:
Disk group: rootdg
TY NAME     ASSOC      KSTATE  LENGTH   PLOFFS  STATE  TUTIL0 PUTIL0
dg rootdg   rootdg     -       -        -       -      -      -
dm disk01   c0b0t1d0s7 -       71793462 -       -      -      -
dm disk02   c0b0t2d0s7 -       71793462 -       -      -      -

In both of the above outputs indicates that "vxinstall" was successful and our three ODM disks are ready be used for RAID-1 (Mirror).

Now to define a RAID-1 "mirror" via ODM.

4-

The best and comfortable way to define a RAID-1 (Mirror) on ODM and associate filesystems on it is via the ODM graphical interface.

This is why it is recommended that you have X-windows working on OSR6 as noted in the "before you start" section.

You can use the ODM command line Interface CLI, but the syntax is long and complicated.

Login as root in the X-scologin screen.

To start ODM GUI Manager, click on the "System Administration" icon, and then the "VERITAS Volume Manager" ico. Or From the xterm, run:

# vxva &

This will open "VERITAS Visual Administrator" window.

To define a simple mirror, please follow the steps:

- Click on the <rootdg> button. this will open a "view of rootdg (<server name>)" window

- From the above menus, choose: Options --> Popup the Command window

This will open a "command Info window" so that we can see what command are run and their progress.

This is good, because if any error happens, we will know at which stage and command it failed....etc

- On the "View of rootdg" window, click with the left mouse button disk01 icons. Disk01 will then be highlighted in green colour.

- In our example, We now will create two VxFS filesystems on disk01 (u1 10 GB & u2 26 GB)

Basic-Ops --> File system Operation --> Create --> Simple

This will open a "Simple Volume/FS Create Form" window. update only the following fields for u1 filesystem:

Volume name = u1 Volume size = 20971520 (The size in 512 blocks = 10 GB) Impose inode limit = No Mount Point = /u1

Then click on the "Apply" button. You will then see on the "command Info window" the commands lines that ODM runs in order to generate that filesystem. Check that all command are successful and have finished with "DONE"

The same you do for u2 filesystem:

Volume name = u2 Volume size = 50790400 *** Impose inode limit = No Mount Point = /u2

*** Note VERY IMPORTANT:

For /u filesystem, we DID NOT enter the maximum allowed space of 50825216, we left 34816 unused (approx. 17 MB).

WHY?

ODM needs some space in the slice 15, Volume Management Private Slice ( Configuration data storage) for it to perform its operations. A max size of 20 MB is more then enough.

In our example, we left 17 MB free space for division 15.

- Now to mirror u1 & u2 to disk02 Hold the <Ctrl> key and click on the left mouse button both the volume "V" u1 icon (NOT the rectangular u1-01 or disk-1-01) & disk02 icon.

- Basic-Ops --> Volume Operations --> Add Mirror --> Simple Mirror

ODM will now start to mirror the /u1 filesystem from disk01 to disk02. You will see the command that it runs from the "command Info window" windows, under the "commands running" section.

Do the Same for u2 filesystems.

The Mirroring of u1 & u2 might take some time, depending on their sizes.

Once it has finished, you can see from the VERITAS GUI if the mirror was success or not.

You can also check the mirror from the command line:

# vxprint -Ath
Disk group: rootdg
TY NAME       ASSOC      KSTATE   LENGTH   PLOFFS   STATE
dg rootdg     rootdg     -        -        -        -
dm disk01     c0b0t1d0s7 -        71798428 -        -
dm disk02     c0b0t2d0s7 -        71793462 -        -
v  u1         fsgen      ENABLED  20971520 -        ACTIVE
pl u1-01      u1         ENABLED  20971520 -        ACTIVE
sd disk01-01  u1-01      ENABLED  20971520 0        -
pl u1-02      u1         ENABLED  20971520 -        ACTIVE
sd disk02-01  u1-02      ENABLED  20971520 0        -
v  u2         fsgen      ENABLED  50790400 -        ACTIVE
pl u2-01      u2         ENABLED  50790400 -        ACTIVE
sd disk01-02  u2-01      ENABLED  50790400 0        -
pl u2-02      u2         ENABLED  50790400 -        ACTIVE
sd disk02-02  u2-02      ENABLED  50790400 0        -

The "Active" is what we are looking for to indicate the success of the mirror and its status.

For more options on the vxprint command, see man pages vxprint(ADM).

Recovering from a broken Mirror (Faulty disk)
---------------------------------------------

In the event of a faulty disk, ODM will mark it as faulty and the mirror gets detached.

Lets assume that Disk02 (ODM Naming) got faulty, you will see this:

# vxprint
Disk group: rootdg
TY NAME       ASSOC      KSTATE   LENGTH   PLOFFS  STATE
dg rootdg     rootdg     -        -        -       -
dm disk01     c0b0t1d0s7 -        71798428 -       -
dm disk02     -          -        -        -       NODEVICE
v  u1         fsgen      ENABLED  20971520 -       ACTIVE
pl u1-01      u1         ENABLED  20971520 -       ACTIVE
sd disk01-01  u1-01      ENABLED  20971520 0       -
pl u1-02      u1         DISABLED 20971520 -       NODEVICE
sd disk02-01  u1-02      DISABLED 20971520 0       NODEVICE
v  u2         fsgen      ENABLED  50790400 -       ACTIVE
pl u2-01      u2         ENABLED  50790400 -       ACTIVE
sd disk01-02  u2-01      ENABLED  50790400 0       -
pl u2-02      u2         DISABLED 50790400 -       NODEVICE
sd disk02-02  u2-02      DISABLED 50790400 0       NODEVICE

As you can see, disk02 has a "STATE" of "NODEVICE", which means ODM can't access it and has been detached.

To replace the faulty disk02 and recover the ODM mirror, you need to carry out the following steps:

1- Run as root the "vxdiskadm" command line:

# vxdiskadm

From the menu, choose "4 - Remove a disk for replacement"

Remove a disk for replacement
Menu: VolumeManager/Disk/RemoveForReplace

Use this menu operation to remove a physical disk from a disk group, while retaining the disk name. This changes the state for the disk name to a "removed" disk. If there are any initialized disks that are not part of a disk group, you will be given the option of using one of these disks as a replacement.

Enter disk name [<disk>,list,q,?] <disk02>
Enter "disk02" as the  name. If you do not know the name,
enter "l" for list of disks in the "rootdg" and the list
below will be shown:
Disk group: rootdg
DM NAME     DEVICE      TYPE    PRIVLEN  PUBLEN   STATE
dm disk01   c0b0t1d0s7  sliced  1024     71798428 -
dm disk02   -           -       -        -        NODEVICE
Enter disk name [<disk>,list,q,?] <disk02>
Type "disk02".

The following volumes will lose mirrors as a result of this operation:

u1 u2

No data on these volumes will be lost.

The requested operation is to remove disk disk02 from disk group rootdg. The disk name will be kept, along with any volumes using the disk, allowing replacement of the disk.

Select "Replace a failed or removed disk" from the main menu when you wish to replace the disk.

Continue with operation? [y,n,q,?] (default: y) <RETURN>

Hit RETURN to choose the default "y".

Remove another disk? [y,n,q,?] (default: n) <RETURN>

Hit RETURN to choose the default "n", then q to quit "vxdiskadm".

"vxprint" will now show this output:
# vxprint
Disk group: rootdg
TY NAME       ASSOC      KSTATE   LENGTH   PLOFFS  STATE
dg rootdg     rootdg     -        -        -       -
dm disk01     c0b0t1d0s7 -        71798428 -       -
dm disk02     -          -        -        -       REMOVED
v  u1         fsgen      ENABLED  20971520 -       ACTIVE
pl u1-01      u1         ENABLED  20971520 -       ACTIVE
sd disk01-01  u1-01      ENABLED  20971520 0       -
pl u1-02      u1         DISABLED 20971520 -       REMOVED
sd disk02-01  u1-02      DISABLED 20971520 0       REMOVED
v  u2         fsgen      ENABLED  50790400 -       ACTIVE
pl u2-01      u2         ENABLED  50790400 -       ACTIVE
sd disk01-02  u2-01      ENABLED  50790400 0       -
pl u2-02      u2         DISABLED 50790400 -       REMOVED
sd disk02-02  u2-02      DISABLED 50790400 0       REMOVED
Shutdown the server and power off.

2- Remove the faulty disk and replace it with a new one.

Note: IMPORTANT!!!

The new disk MUST be the exact same size (or more) as the active disk. If the replaced disk is even one cylinder less then the active disk, then the ODM can't repair the mirror.

Therefore it is highly recommended to have the replaced disk from the same size and make of the active disk.

3- Boot the Server.

As root, you need to initialize the replaced disk under SCO OpenServer 6.0.0. Follow the same procedure in the Section "Setting UP a Mirror" - Step 1.

4- Run the following commands as root:

# /usr/sbin/vxdctl stop
# /usr/sbin/vxconfigd -k -m enable
# /usr/sbin/vxdctl enable

The above commands will restart ODM so that it will be aware of the new replaced disk.

5- Run the "vxdiskadm" from the command line.

# vxdiskadm

From the menu, choose "5 - Replace a failed or removed disk"

Replace a failed or removed disk
Menu: VolumeManager/Disk/ReplaceDisk

Use this menu operation to specify a replacement disk for a disk that you removed with the "Remove a disk for replacement" menu operation, or that failed during use. You will be prompted for a disk name to replace and a disk device to use as a replacement. You can choose an uninitialized disk, in which case the disk will be initialized, or you can choose a disk that you have already initialized using the Add or initialize a disk menu operation.

Select a removed or failed disk [<disk>,list,q,?]
<disk02>
Enter "disk02" (Our replaced disk).
Select disk device to initialize [<address>,list,q,?]
<c0b0t2d0>

Enter "c0b0t2d0", which is our Device for the replaced disk. With "l" you can see all the list of Devices ODM has knowledge of.

If the new replaced disk had before a valid VTOC, then ODM will allow you to preserve the data via encapsulation.

Then you get the below message. We do not want to encapsulate but initialize.

If the disk was brand new, then you are asked to initialize the disk:

The following disk device has a valid VTOC, but does not appear to have been initialized for the Volume Manager. If there is data on the disk that should NOT be destroyed you should encapsulate the existing disk partitions as volumes instead of adding the disk as a new disk. Output format: [Device_Name]

c0b0t2d0
Encapsulate this device? [y,n,q,?] (default: y) <n>
Enter "n", for not encapsulating.
Instead of encapsulating, initialize? [y,n,q,?] (default: n)
<y>
Enter "y" for initialization.

The requested operation is to initialize disk device c0b0t2d0 and to then use that device to replace the removed or failed disk disk02 in disk group rootdg.

Continue with operation? [y,n,q,?] (default: y) <RETURN>
Hit RETURN for the default "y"
Perform surface analysis (highly recommended)
[y,n,q,?] (default: y) <n>

PLEASE CHOOSE "n" and ignore the recommended, as this will take ages to finish. Not really needed for SCSI HDs.

Replace another disk? [y,n,q,?] (default: n) <RETURN>
Hit RETURN for default "n".

Still in the "vxdiskadm" menu, you can see if the above operation was successful or not, by choosing "l" for "List disk information" and then default "all".

You will see this output, where disk02 now is reporting online for ODM:

DEVICE     DISK      GROUP     STATUS
c0b0t0d0   -         -         error
c0b0t1d0   disk01    rootdg    online
c0b0t2d0   disk02    rootdg    online

6- ODM is now re-syncing the data (u1 & u2) from disk01 to the replaced mirror disk02. To check, run "vxprint":

# vxprint
Disk group: rootdg
TY NAME       ASSOC      KSTATE   LENGTH   PLOFFS  STATE
dg rootdg     rootdg     -        -        -       -
dm disk01     c0b0t1d0s7 -        71798428 -       -
dm disk02     c0b0t2d0s7 -        71793462 -       -
v  u1         fsgen      ENABLED  20971520 -       ACTIVE
pl u1-01      u1         ENABLED  20971520 -       ACTIVE
sd disk01-01  u1-01      ENABLED  20971520 0       -
pl u1-02      u1         ENABLED  20971520 -       STALE
sd disk02-01  u1-02      ENABLED  20971520 0       -
v  u2         fsgen      ENABLED  50790400 -       ACTIVE
pl u2-01      u2         ENABLED  50790400 -       ACTIVE
sd disk01-02  u2-01      ENABLED  50790400 0       -
pl u2-02      u2         DISABLED 50790400 -       RECOVER
sd disk02-02  u2-02      ENABLED  50790400 0       -

ODM can only re-sync one filesystem at a time.

From the above output, "STALE" means that this filesystem is been currently synced and "RECOVER" means, this filesystem is on the queue to be synced.

The syncing will take a while depending on the filesystem sizes (our example u1 & u2).

NOTES:    As a reminder, these point are important to remember when
          configuring Mirroring under ODM and recovery:

1- If you are only using ODM Mirroring, then you only need SCO OpenServer 6 Disk Mirroring License and not the full SCO OpenServer 6 Online Data Manager License.

2- It is highly recommended that both Mirror Disks needs to of the same size and make.

If disk01 is smaller then disk02, then ODM will use Disk01 as the reference disk size, thus you will loose disk space on the disk02.

3- Replaced Faulty disk under ODM MUST be of the same size or more of the active (good) one.

NEVER EVER replace the faulty disk with a smaller one then the active disk01.

For example: Disk01 = 35070 MB Disk02 = 35070 MB When disk disk02 becomes faulty, then the new replaced disk02 MUST be 35070 MB or More (and NOT less then 35070 MB).

4- Disks MUST BE initialized  first via "mkdev hd" before
it can be used by ODM.

5- ODM Mirrors filesystems and not the whole physical disk.

6- Make sure you DO NOT use the whole disk space when you define a filesystem via ODM. Leave some small amount of disk space (20 MB is good) for ODM temp allocation files.

See also

http://osr600doc.xinuos.com/en/ODM_oi/_Online_Data_Manager_oi.html

From the Xinuos technical article database, record 126802. Reproduced with permission. The original is at www.sco.com/ta/126802, which is reachable but blocked from search engines.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.