增加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 -help
chiogrpUse the chiogrp command to modify the name of an I/O group, or the
amount 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 of
memory that is available for RAID arrays, Copy Services, or volume
mirroring.Use the -feature and -size parameters (together) to change the amount of
memory 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 specified
I/O group. You can change the amount of memory that is available for
RAID arrays, Copy Services, or volume mirroring operations by specifying
the -feature local | remote | mirror parameter - and a memory size. For
volume mirroring and Copy Services (Local Copy(r), Sync Copy, Async Copy,
and InMetro), memory is traded against memory that is
available to the cache. The amount of memory can be decreased or increased. Consider the
following 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 grou
Sync Copy, Async Copy, Volume Mirroring, and RAID share 1064 MB of
bitmap 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 RAID
arrays, Copy Services, and volume mirroring. Each 1 MB of memory
provides 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 bitmap
memory cost, where MS is the size of the member drives and MC is the
number 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 of
mappings. For example, for a mapping with a 256 KB grain size, 8 KB of
memory allows one mapping between a 16 GB source volume and a 16 GB
target volume. Alternatively, for a mapping with a 256 KB grain size, 8
KB of memory allows two mappings between one 8 GB source volume and two
8 GB target volumes.Afte you create a Local Copy(r) mapping, if you specify an I/O group other
than the I/O group of the source volume, the memory accounting goes
towards the specified I/O group, not towards the I/O group of the source
volume.An invocation example to create a new I/O group testiogrpone
chiogrp -name testiogrpone io_grp0The resulting output:No feedbackAn invocation example for changing the amount of Local Copy(r) memory in
io_grp0 to 30 MB
chiogrp -feature local -size 30 io_grp0The resulting output:No feedbackAn invocation example for changing the amount of RAID memory in I/O
group 0 to 512 MB
chiogrp -feature raid -size 512 0The resulting output:No feedback

我这做了分布式Raid6容量110T,按上面1M/B 每2TB,仅这一项至少得60MB的内存

增加I/O组0和1的内存

chiogrp -feature local -size 120 0
chiogrp -feature local -size 120 1

尝试创卷或池

已经操作成功

再次lsiogrp 0 lsiogrp 1查看

2个I/O组还剩余19.5M,也就是说Local_copy至少100MB才够,
其他的remote\mirror内存可以参靠Help里面的提示操作。


我把remote和mirroring内存都做了增加,留一点余量,后续操作也方便

浪潮存储新建池、创建卷提示I/O组内存不足、I/O空间位置不足解决方法相关推荐

  1. 计算机任务计划程序已损坏,win10创建任务提示“该任务映像已损坏或已篡改”的解决方法...

    win10系统任务管理器是非常重要的,提供了有关计算机性能的信息,并显示计算机程序和进程的详细信息.win10系统在在任务管理器创建任务时弹出提示"该任务映像已损坏或已篡改"怎么解 ...

  2. 创建虚拟机时提示“已拒绝虚拟机配置。请参见浏览器控制”的解决方法

    创建虚拟机时提示"已拒绝虚拟机配置.请参见浏览器控制"的解决方法 上面的问题出现在 VMwareESXi 6.5u2和VMwareESXi 6.7环境下,当然其他环境也会出现 这个 ...

  3. mac u盘文件过大 拷贝不进去_U盘拷贝文件提示目标文件过大无法复制到U盘的解决方法...

    我们经常需要使用U盘来存储文件,但是在拷贝文件的时候却提示目标文件过大无法复制到U盘,但是查看U盘的存储空间肯定是足够的,那么问题有可能出在U盘的格式上.一般来说,fat32格式的U盘只允许拷贝或者创 ...

  4. cant connect local mysql to_连接Mysql提示Can't connect to local MySQL server through socket的解决方法...

    mysql,mysqldump,mysqldump,php连接mysql服务常会提示下面错误: ERROR 2002 (HY000): Can't connect to local MySQL ser ...

  5. mysql5.7更改数据库存储位置_mysql 5.7更改数据库的数据存储位置的解决方法

    随着mysql数据库存储的数据逐渐变大,已经将原来的存储数据的空间占满了,导致mysql已经链接不上了.因此,必须要给存放的数据换个地方了.下面是操作过程中的一些步骤.记下来,以后日后查看. 1.修改 ...

  6. 计算机提示无法验证发布者,win10提示无法验证发布者所以windows已阻止此软件的解决方法【图文教程】...

    近来,有不少win10系统用户反映自己在使用某些软件的时候,系统总是会提示由于无法验证发布者所以windows已阻止此软件,这该怎么办呢?接下来,小编就向大家分享win10提示无法验证发布者所以win ...

  7. 电脑计算机提示msvcr100.dll丢失如何修复,msvcr100.dll丢失的解决方法

    电脑计算机提示msvcr100.dll丢失如何修复,msvcr100.dll丢失的解决方法?系统文件msvcp100.dll是存放在Windows系统文件夹中的重要文件,通常情况下是在安装操作系统过程 ...

  8. 无法启动计算机中丢失HAL.dll,win7系统提示“hal.dll损坏或丢失”导致windows无法启动的解决方法...

    今天和大家分享一下win7系统提示"hal.dll损坏或丢失"导致windows无法启动问题的解决方法,在使用win7系统的过程中经常不知道如何去解决win7系统提示"h ...

  9. 安装VM虚拟机提示 尝试创建目录 C:\Public\documents\SharedVirtual Machines 时发生错误解决方法

    安装VM虚拟机提示 尝试创建目录 C:\Public\documents\SharedVirtual Machines 时发生错误解决方法 参考文章: (1)安装VM虚拟机提示 尝试创建目录 C:\P ...

最新文章

  1. 如何在React Native中记录日志?
  2. 多种方式读取文件内容
  3. 电话号码的字母组合Python解法
  4. 微信小程序点击复制文本到剪切板,获取剪切板内容
  5. apk安装到电视上看不到图标_零基础搭建电视直播APP平台第二弹(修改APP)
  6. springboot1.5.4 log4j
  7. 信息化项目软件运维费用都有哪些构成?
  8. QPointer、QScopedPointer、QSharedDataPointer等指针用法总结
  9. 从苏宁电器到卡巴斯基第22篇:单证这一年(下)
  10. xbox手柄适配器驱动_用于Windows的Xbox 360控制器无线接收器适配器
  11. 近5年内有关病毒在复杂网络中传播与控制方面的20篇论文
  12. ci发什么音标_单词发[ci]的单词有哪些,音标和中文又是什么?
  13. linux下怎样安装openmpi
  14. OpenCV-Python学习之(一)waitKey()函数详解
  15. 有关PHP文档生成工具---PHPDocumentor
  16. 对话框屏蔽Esc键的方法
  17. etc通行费发票怎么打印?通行费发票打印步骤
  18. 雷达数据 障碍物判断_数据科学的进入障碍
  19. 怎样打开xp默认共享?
  20. unity 3D场景摄像机跟随人物

热门文章

  1. 动态规划算法之资源分配问题及其空间优化方案
  2. [书目20100320]首先,打破一切常规
  3. OpenOffice3将支撑PDF编纂及ac琐屑
  4. 天清江月白,心静海鸥知 (4.26每周总结)
  5. (附源码)ssm华辰酒店管理系统 毕业设计 021206
  6. 007.西门子M440变频器模拟量给定(变频器频率随着温度的变化而变化)
  7. 支付宝APP支付申请
  8. 基于google升级版c++代码规范指南
  9. 如何使用 Tibco Business Works 6 (BW6) 或容器版 (BWCE) 创建 Restful Web 服务
  10. 18个演讲PPT技巧,让你成为真正的演讲高手