Network Storage Protocols Discussions

aggr add in a metrocluster

syscomnoumea

Hello,

I am on a IBM nserie in a metrocluster concept.

I have an aggr aggrCapsSataCifs who is active in only plex1

Aggregate aggrCapsSataCifs (online, raid_dp) (block checksums)
Plex /aggrCapsSataCifs/plex1 (online, normal, active, pool1)
RAID group /aggrCapsSataCifs/plex1/rg0 (normal, block checksums)

  RAID Disk Device HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity   SW-METRO-CLEM-H:5.126L111 3a    15  6   FC:A   1  BSAS 7200 1695466/3472315904 1695759/3472914816
parity SW-METRO-CLEM-B:5.126L8 3b    15  7   FC:B   1  BSAS 7200 1695466/3472315904 1695759/3472914816
data SW-METRO-CLEM-B:5.126L9 3b    15  8   FC:B   1  BSAS 7200 1695466/3472315904 1695759/3472914816
data SW-METRO-CLEM-H:5.126L114 3a    15  9   FC:A   1  BSAS 7200 1695466/3472315904 1695759/3472914816

I have some disk who is assign to the pool0 spare and ready

Pool1 spare disks

RAID Disk       Device                          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------       ------                          ------------- ---- ---- ---- ----- --------------    --------------
Spare disks for block checksum
spare           SW-METRO-CLEM-B:5.126L27        3b    11  0   FC:B   1   SAS 15000 418000/856064000  420584/861357448
spare           SW-METRO-CLEM-B:5.126L53        3b    12  0   FC:B   1   SAS 15000 418000/856064000  420584/861357448
spare           SW-METRO-CLEM-B:5.126L79        3b    13  0   FC:B   1   SAS 15000 418000/856064000  420584/861357448
spare           SW-METRO-CLEM-B:5.126L13        3b    15  12  FC:B   1  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CLEM-B:5.126L14        3d    15  13  FC:B   1  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CLEM-B:5.126L19        3d    15  18  FC:B   1  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CLEM-B:5.126L20        3b    15  19  FC:B   1  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CLEM-B:5.126L21        3b    15  20  FC:B   1  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CLEM-B:5.126L22        3b    15  21  FC:B   1  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CLEM-B:5.126L23        3d    15  22  FC:B   1  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CLEM-B:5.126L24        3d    15  23  FC:B   1  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CLEM-H:5.126L116       3a    15  11  FC:A   1  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CLEM-H:5.126L121       3c    15  16  FC:A   1  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CLEM-H:5.126L122       3c    15  17  FC:A   1  BSAS  7200 1695466/3472315904 1695759/3472914816

Pool0 spare disks

RAID Disk       Device                          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------       ------                          ------------- ---- ---- ---- ----- --------------    --------------
Spare disks for block checksum
spare           SW-METRO-CAPS-H:5.126L87        3a    1   8   FC:A   0   SAS 15000 418000/856064000  420584/861357448
spare           SW-METRO-CAPS-H:5.126L76        3a    2   23  FC:A   0   SAS 15000 418000/856064000  420584/861357448
spare           SW-METRO-CAPS-B:5.126L7         3b    5   6   FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816 (zeroing, 3% done)
spare           SW-METRO-CAPS-B:5.126L8         3b    5   7   FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816 (zeroing, 3% done)
spare           SW-METRO-CAPS-B:5.126L9         3b    5   8   FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816 (zeroing, 3% done)
spare           SW-METRO-CAPS-B:5.126L10        3b    5   9   FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816 (zeroing, 3% done)
spare           SW-METRO-CAPS-B:5.126L12        3b    5   11  FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CAPS-B:5.126L13        3d    5   12  FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CAPS-B:5.126L14        3d    5   13  FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CAPS-B:5.126L17        3b    5   16  FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CAPS-B:5.126L18        3d    5   17  FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CAPS-B:5.126L19        3b    5   18  FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CAPS-B:5.126L20        3b    5   19  FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CAPS-B:5.126L23        3d    5   22  FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CAPS-B:5.126L24        3d    5   23  FC:B   0  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CAPS-H:5.126L125       3c    5   20  FC:A   0  BSAS  7200 1695466/3472315904 1695759/3472914816
spare           SW-METRO-CAPS-H:5.126L126       3a    5   21  FC:A   0  BSAS  7200 1695466/3472315904 1695759/3472914816

I would like to assign this disk to my aggregate to begin the syncmirror processe

aggr add aggrCapsSataCifs -d SW-METRO-CAPS-B:5.126L12 SW-METRO-CAPS-B:5.126L13 SW-METRO-CAPS-B:5.126L14 SW-METRO-CAPS-B:5.126L17

but it's say that I am in the wrong pool and that I should use the -f option

aggr add: Disk 'SW-METRO-CAPS-B:5.126L12' is from the wrong pool. Use the -f option to override this check.

Why does it say that. and can I use -F options

thanks for your help.


1 REPLY 1

aborzenkov

You need to use disks from pool1, as in you aggregate.

Announcements
NetApp on Discord Image

We're on Discord, are you?

Live Chat, Watch Parties, and More!

Explore Banner

Meet Explore, NetApp’s digital sales platform

Engage digitally throughout the sales process, from product discovery to configuration, and handle all your post-purchase needs.

NetApp Insights to Action
I2A Banner
Public