Assessments - 0, GPA: 0
(
)
)
|
Facilidade de uso
RAID Array 450 HSZ50 HSOF Software Version 5.7 for Compaq Tru64 UNIX
10.0 Possible Problem Identified
Read this section if you initialized a JBOD disk using the
SAVE_CONFIGURATION switch on an HSZ40 controller running HSOF
Version 2.7, and then moved the disk to your HSZ50 controller subsystem.
There is a remote possibility that some disks attached to HSZ40/20/SWXRC
controllers and the solution products containing them (RA410, SC4200/4600,
etc.) might have a problem in the structure of the on-disk file system. Systems
which might be affected are those which:
1. Use disks in JBOD configurations (that is, disks which are not members of
controller-based storagesets such as RAIDsets and mirrorsets)
2. Initialized disks under HSOF Version 2.7 software using the INITIALIZE
SAVE_CONFIGURATION command AND rebooted the controller
BEFORE initializing the disk under the operating system.
Note that the problem does not occur if the file system was built on the disk
before the controller was rebooted. Also, the problem does not occur when
disks are initialized using the SAVE_CONFIGURATION switch and the
platform operating system under HSOF Versions 30Z, and above AND 50Z,
and above.
If a disk built as described above is moved to an HSZ50 controller running
HSOF Version 5.0 and above, problems could occur.
When a disk being used in a JBOD configuration is initialized with the
SAVE_CONFIGURATION switch, the last 500 blocks on the disk are allocated
by the controller to store the configuration data. If the controller running HSOF
Version 27Z software is rebooted before the disk is initialized by the platform
operating system, the controller fails to remember the reduction in disk size
and reports the unreduced disk capacity to the operating system. When the
operating system subsequently builds the file system, the blocks which
INITIALIZE SAVE_CONFIGURATION uses to update the configuration data
are also included in the file system disk space, creating a potential for both the
operating system and the controller to write to the last 500 blocks on disk.
If the file system subsequently overwrites configuration data, the controller
recognizes that the data is invalid configuration data and ignores it. In this
case, controller parameters must be manually re-entered when the INITIALIZE
container-name SAVE_CONFIGURATION command tries to restore the
configuration (unless another drive contains valid configuration data).
Page 82
AA–R1ZZE−TE
... Este manual também é adequado para os modelos :
Software - Tru64 UNIX 4.0G (204.92 kb)
Software - Tru64 UNIX 5.0 (204.92 kb)
Software - Tru64 UNIX 5.0A (204.92 kb)
Software - Tru64 UNIX 5.1 (204.92 kb)