Technical article 104965

divvy overlaps the recover area when creating a filesystem at install time.

OpenServer 5.0.0

Written · Last revised

Problem

I am installing an SCO OpenServer Release 5.0 system and I am using the "Interactive fdisk/divvy" feature of the Installation Query Manager (IQM).

I am prompted by divvy(ADM) as follows:

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)

When I answer yes, this table is displayed:

+-------------------+------------+--------+---+-------------+------------+
| Name              | Type       | New FS | # | First Block | Last Block |
+-------------------+------------+--------+---+-------------+------------+
| boot              | EAFS       |  yes   | 0 |            0|       14999|
| swap              | NON FS     |  no    | 1 |        15000|       29999|
| root              | HTFS       |  yes   | 2 |        30000|      531732|
|                   | NOT USED   |  no    | 3 |            -|           -|
|                   | NOT USED   |  no    | 4 |            -|           -|
|                   | NOT USED   |  no    | 5 |            -|           -|
| recover           | NON FS     |  no    | 6 |       531733|      531742|
| d1157all          | WHOLE DISK |  no    | 7 |            0|      532238|
+-------------------+------------+--------+---+-------------+------------+
531743 1K blocks for divisions, 496 1K blocks reserved for the system
I want to reduce the size of root and add an additional filesystem
in the space that I have freed up.  I first use "e[nd]" to reduce
the number of blocks in root. The result is:
+-------------------+------------+--------+---+-------------+------------+
| Name              | Type       | New FS | # | First Block | Last Block |
+-------------------+------------+--------+---+-------------+------------+
| boot              | EAFS       |  yes   | 0 |            0|       14999|
| swap              | NON FS     |  no    | 1 |        15000|       29999|
| root              | HTFS       |  yes   | 2 |        30000|      500000|
|                   | NOT USED   |  no    | 3 |            -|           -|
|                   | NOT USED   |  no    | 4 |            -|           -|
|                   | NOT USED   |  no    | 5 |            -|           -|
| recover           | NON FS     |  no    | 6 |       531733|      531742|
| d1157all          | WHOLE DISK |  no    | 7 |            0|      532238|
+-------------------+------------+--------+---+-------------+------------+
531743 1K blocks for divisions, 496 1K blocks reserved for the system

I then use "n[ame]" to name division 3 and "s[tart]" to specify a start block of 500001. The result of issuing these two commands is:

+-------------------+------------+--------+---+-------------+------------+
| Name              | Type       | New FS | # | First Block | Last Block |
+-------------------+------------+--------+---+-------------+------------+
| boot              | EAFS       |  yes   | 0 |            0|       14999|
| swap              | NON FS     |  no    | 1 |        15000|       29999|
| root              | HTFS       |  yes   | 2 |        30000|      500000|
| u                 | NOT USED   |  no    | 3 |       500001|      531742|
|                   | NOT USED   |  no    | 4 |            -|           -|
|                   | NOT USED   |  no    | 5 |            -|           -|
| recover           | NON FS     |  no    | 6 |       531733|      531742|
| d1157all          | WHOLE DISK |  no    | 7 |            0|      532238|
+-------------------+------------+--------+---+-------------+------------+
531743 1K blocks for divisions, 496 1K blocks reserved for the system
Note how the "u" division overlaps the recover area.  This is
caused by a fault in the automatic calculation of the "e[nd]"
block that is calculated by divvy(ADM).

Solution

You can use the "e[nd]" menu choice to specify the correct end
block value for the "u" division.  In the example above, the
correct end block is 531732.

This problem has been reported to SCO Engineering.

From the Xinuos technical article database, record 104965. Reproduced with permission. The original is at www.sco.com/ta/104965, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

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.