Оценок - 0, средний балл: 0
(
)
)
|
К этому устройству также есть другие инструкции:
Фрагмент инструкции
2.05 using the following URL and copy the firmware update to each G6 server. Follow the installation
instructions noted in the URL. This issue does not affect G7 servers.
http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=us&
prodTypeId=15351&prodSeriesId=1146658&swItem=MTX-949698a14e114478b9fe126499&
prodNameId=1135772&swEnvOID=4103&swLang=8&taskId=135&mode=3
Snapshot behavior for file systems created under an earlier release
To take snapshots of files, they must be created on X9000 File Serving Software 6.0 or later. (These
files are referred to as snapable.) To accommodate software snapshots, the inode format has changed
in the 6.0 release. For file systems created in a release earlier than 6.0, X9000 software can preserve
all name space data in snapshots but can preserve file data only for objects (files) created under
release 6.0 or later.
To help prevent “hybrid snap trees,” in which a snap tree contains objects with the old format, the
6.0 release implements restrictions on rename operations. The following restrictions apply to hybrid
file systems:
•
Only directories created in version 6.0 or later can become snap tree roots.
•
If the old directory is not in a snap tree and the new directory is in a snap tree, rename is allowed
only if the object being renamed is snapable (that is, it has the new format).
The following restrictions apply to both hybrid file systems and pure 6.0 file systems:
•
A snap tree root cannot be renamed. Also, the path to a snap tree root cannot be changed.
•
Rename is allowed when neither the old directory or the new directory are in snap trees.
•
Rename is allowed when the old directory and the new directory are in the same snap tree.
Rename is not allowed when the directories are in different snap trees.
These restrictions are intended to prevent hybrid snap trees containing files with the old format. However,
hybrid snap trees can still occur when a directory having the new format is populated, using rename,
with old format objects and that directory is then made into a snap tree root or is renamed into a snap
tree. The X9000 software does not prevent this situation because it could take a prohibitively long
amount of time to perform a complete scan for old objects in the sub tree being moved if the new sub
tree was sufficiently large.
Implementation changes
The following changes have been made in this release.
Agile management console
The agile management console is now required on all file serving nodes. The management console is
active on one node and passive on the other nodes.
Spillover
Spilling over sequentially written files from one segment to another is disabled in the 6.0 release; no
new spillover chunks will be created. If a segment is full, writes to files in that segment will fail with
-ENOSPC (-28), even if there is space available in other segments. Existing spillover files generated
in the 5.x release will continue to work (read/write). Writes will continue to work if there is space
available in the segments to which the file belongs. If the segments are full, writes will fail with
–ENOSPC.
Existing spillover files cannot be snapped and cannot be moved into a snap tree.
To minimize out-of-space errors when creating files, it is important to ensure that segments are balanced.
If some segments are over 80% full and other segments are less than 80% full, it is advisable to run
a segment rebalance task.
New features
5
...Эта инструкция также подходит к моделям:
Устройства обработки данных - HP IBRIX X9320 10GbE Performance Block (307.15 kb)
Устройства обработки данных - HP IBRIX X9320 IB Performance Block (307.15 kb)
Устройства обработки данных - HP StoreAll 8800 Storage Node (307.15 kb)
Устройства обработки данных - HP StoreAll 9320 1GbE Storage Node Pair (307.15 kb)