增加I/O组内存chiogrp
使用终端工具登录到存储
使用用lsiogrp id查看I/O组信息，例如查看I/O组0可输入lsiogrp 0
此时可以看到
local_copy_total_memory 20.0MB
I/O组内存为20M
更改I/O组内存可以通过chiogrp命令修改
可以通过chiogrp -help查看各个操作需要内存
Inspur_MCS:Cluster_192.168.70.10:superuser>chiogrp -helpchiogrpUse the chiogrp command to modify the name of an I/O group, or theamount of memory that is available for RAID arrays, Copy Services,LocalCopy(r) services, or volume mirroring operations.Syntax >>- chiogrp -- ------------------------------------------------->>--+------------------------------------------------------------------+-->+- -name -- new_name ----------------------------------------------+ +- ----------------------------------------------------------------+ '- -feature --+- local --+-- -- -size ---- memory_size --+-------+-' +- remote -+ '- -kb -'+- mirror -+'- raid ---'>--+-------------------------+---------------------------------->'- -maintenance --+-----+-' +-yes-+'-no--'>--+---------------------------------------+--+------------+---->'- -fctargetportmode --+-disabled-----+-' '- -force ---' +-transitional-+ '-enabled------' >--+- io_group_id ---+-----------------------------------------><'- io_group_name -' Parameters-name new_name(Optional) Specifies the name to assign to the I/O group. The -nameparameter cannot be specified with the -feature, -size, or -kbparameters.-feature local | remote | mirror | raid(Optional) Specifies the feature to modify the amount of memory forRAID arrays, Copy Services, or volume mirroring. You must specifythis parameter with the -size parameter. You cannot specify thisparameter with the -name parameter. * local specifies the amount of memory that is used for LocalCopy.* remote specifies the amount of memory that is used for remote copyprocessing. Remote copy includes Sync Copy, Async Copy, andInMetro.* mirror specifies the amount of memory that is used for volumemirroring operations.* raid specifies the amount of memory that is used for RAID arrays.Note: Specifying remote changes the amount of memory that isavailable for remote copy processing. Any volume that is in a remotecopy relationship uses memory in its I/O group, including master andauxiliary volumes, and volumes that are in inter-system orintra-system relationships.-size memory_size(Optional) Specifies the amount of memory that is available for thespecified RAID arrays, Copy Services, or volume mirroring function.Valid input is 0 or any integer. The default unit of measurement forthis parameter is megabytes (MB); you can use the kilobytes -kbparameter to override the default. You must specify this parameterwith the -feature parameter. You cannot specify this parameter withthe -name parameter.-kb(Optional) Changes the units for the -size parameter from megabytes(MB) to kilobytes (KB). If you specify this parameter, the -sizememory_size value must be any number divisible by 4. You must specifythis parameter with the -feature and -size parameters. You cannotspecify this parameter with the -name parameter.-maintenance yes | no(Optional) Specifies whether the I/O group must be in maintenancemode. The I/O group must be placed in maintenance mode whileperforming service procedures on storage enclosures. After you entermaintenance mode, it continues until either: * It is explicitly cleared* Thirty minutes elapseNote: Changing the maintenance mode on any I/O group changes themaintenance mode on all I/O groups.-fctargetportmode disabled | transitional | enabled(Optional) Specifies the Fibre Channel (FC) host port mode of the I/Ogroup. The values are disabled, transitional, or enabled.-force(Optional) Specifies that an FC host port be disabled or enabled,even if disruption to host I/O might occur as a result. You can onlyspecify -force with -fctargetportmode.Important: Specifying -force might result in a loss of access. Use itonly under the direction of the your product support information.io_group_id | io_group_name(Required) Specifies the I/O group to modify. You can modify an I/Ogroup by using the -name or the -feature parameter.DescriptionThe chiogrp command modifies the name of an I/O group or the amount ofmemory that is available for RAID arrays, Copy Services, or volumemirroring.Use the -feature and -size parameters (together) to change the amount ofmemory available in the I/O group to one of the following types: * LocalCopy* Volume mirroring* RAID* Remote copy, including Sync Copy, Async Copy, and InMetro.For example: chiogrp -feature local -size 40 0You can assign a name to an I/O group or change the name of a specifiedI/O group. You can change the amount of memory that is available forRAID arrays, Copy Services, or volume mirroring operations by specifyingthe -feature local | remote | mirror parameter - and a memory size. Forvolume mirroring and Copy Services (Local Copy(r), Sync Copy, Async Copy,and InMetro), memory is traded against memory that isavailable to the cache. The amount of memory can be decreased or increased. Consider thefollowing memory sizes when you use this command: * The default amount of memory for LocalCopy is 20 MB.* The default amount of memory for remote copy (which includes Sync Copy,Async Copy, and InMetro) is 20 MB.* The default memory size for mirrored volumes is 20 MB.* The default memory size for RAID arrays is 40 MB.* The maximum amount of memory that can be specified for LocalCopy is512 MB. For 64-bit systems, the maximum is 2048 MB.* The maximum amount of memory for remote copy (which includes Sync Copy,Async Copy, and InMetro) is 1024 MB.* The maximum memory size that can be specified for mirrored volumes is1024 MB.* The maximum memory size for RAID arrays is 1024 MB.The maximum combined amount of memory across all features is 1064 MB.Some systems running 64-bit mode might have 2 GB of bitmap space to use for LocalCopy,which is enough for 4 PB of data space to be used per I/O grouSync Copy, Async Copy, Volume Mirroring, and RAID share 1064 MB ofbitmap space; in 8GB platform, Sync Copy, Async Copy, Volume Mirroring,and RAID share 552 MB of bitmap space.Table 5 demonstrates the amount of memory that is required for RAIDarrays, Copy Services, and volume mirroring. Each 1 MB of memoryprovides the following volume capacities and grain sizes: Table 5. Memory required for RAID arrays, Copy Services, and volume mirroring+-----------------------+----------------------+----------------------+| Feature | Grain size | 1 MB of memory || | | provides the || | | following volume|| | | capacity for the|| | | specified I/O group |+-----------------------+----------------------+----------------------+| Sync Copy and | 256 KB| 2 TB of total Sync || Async Copy | | Copy and Async || | | Copy volume|| | | capacity |+-----------------------+----------------------+----------------------+| InMetro| 256 KB| 2 TB of total || | | inmetro volume || | | capacity || | | Note: For 2 TB of || | | InMetro volume || | | capacity, 1 MB must || | | be assigned in each || | | caching I/O group. |+-----------------------+----------------------+----------------------+| LocalCopy | 256 KB| 2 TB of total || | | LocalCopy source|| | | volume capacity|+-----------------------+----------------------+----------------------+| LocalCopy | 64 KB| 512 GB of total|| | | LocalCopy source|| | | volume capacity|+-----------------------+----------------------+----------------------+| Incremental LocalCopy | 256 KB| 1 TB of total || | | Incremental|| | | LocalCopysource|| | | volume capacity|+-----------------------+----------------------+----------------------+| Incremental LocalCopy | 64 KB| 256 GB of total|| | | Incremental|| | | LocalCopy source|| | | volume capacity|+-----------------------+----------------------+----------------------+| Volume mirroring| 256 KB| 2 TB of mirrored|| | | volumes |+-----------------------+----------------------+----------------------+Table 6 provides an example of RAID level comparisons with their bitmapmemory cost, where MS is the size of the member drives and MC is thenumber of member drives. Table 6. RAID level comparisons+-------------+----------+--------------+---------+-------------------+| Level | Member | Approximate | Redunda | Approximate || | count | capacity| ncy| bitmap memory|| || | | cost |+-------------+----------+--------------+---------+-------------------+| RAID-0| 1-8| MC * MS| None | (1 MB per 2 TB of || || | | MS) * MC|+-------------+----------+--------------+---------+-------------------+| RAID-1| 2 | MS | 1 | (1 MB per 2 TB of || || | | MS) * (MC/2)|+-------------+----------+--------------+---------+-------------------+| RAID-5| 3-16| (MC-1) * MS | 1 | 1 MB per 2 TB of || || | | MS with a strip || || | | size of 256 KB; || || | | double with strip || || | | size of 128 KB. |+-------------+----------+--------------+---------+-------------------+| RAID-6| 5-16| less than | 2 | || || (MC-2 * MS) | | |+-------------+----------+--------------+---------+-------------------+| RAID-10| 2-16| MC/2 * MS | 1 | (1 MB per 2 TB of || | (evens) | | | MS) * (MC/2)|+---------------------------------------------------------------------+| Note: There is a margin of error on the approximate bitmap memory || cost of approximately 15%. For example, the cost for a 256 KB strip || size for RAID-5 is ~1.15 MB for the first 2 TB of MS.|+---------------------------------------------------------------------+For multiple Local Copy(r) targets, you must consider the number ofmappings. For example, for a mapping with a 256 KB grain size, 8 KB ofmemory allows one mapping between a 16 GB source volume and a 16 GBtarget volume. Alternatively, for a mapping with a 256 KB grain size, 8KB of memory allows two mappings between one 8 GB source volume and two8 GB target volumes.Afte you create a Local Copy(r) mapping, if you specify an I/O group otherthan the I/O group of the source volume, the memory accounting goestowards the specified I/O group, not towards the I/O group of the sourcevolume.An invocation example to create a new I/O group testiogrponechiogrp -name testiogrpone io_grp0The resulting output:No feedbackAn invocation example for changing the amount of Local Copy(r) memory inio_grp0 to 30 MBchiogrp -feature local -size 30 io_grp0The resulting output:No feedbackAn invocation example for changing the amount of RAID memory in I/Ogroup 0 to 512 MBchiogrp -feature raid -size 512 0The resulting output:No feedback
我这做了分布式Raid6容量110T，按上面1M/B 每2TB，仅这一项至少得60MB的内存
增加I/O组0和1的内存
chiogrp -feature local -size 120 0chiogrp -feature local -size 120 1
尝试创卷或池
已经操作成功
再次lsiogrp 0 lsiogrp 1查看
2个I/O组还剩余19.5M，也就是说Local_copy至少100MB才够,
其他的remote\mirror内存可以参靠Help里面的提示操作。
我把remote和mirroring内存都做了增加，留一点余量，后续操作也方便
