Volume Grow Fails

Jgiardino · ‎2019-03-25

Good Afternoon NetApp Community,

I hope we are all having a great start to the week! I am experiencing a bit of oddity against growing a particular volume on my FAS2040. The hidden options command for raid.raid_dp.raidsize.override has been set, I've tried to change the autosize settings to my desired size (30TB) as well as completely disabling autosize. None have worked. I still get that the volume size is too large / unsupported but I have confirmed via Hardware Universe the max size for my 2040 on 8.2 7M should be 30TB. The only thing I can think of I haven't tried is adding more disk count to the underlying aggr. My aggr has the space available as is but do I simply need to increase the raid count to be able to have the vol size command succeed now?

SpindleNinja · ‎2019-03-25

The highest support ontap version I see for the 2040 is 8.1 on HWU.

can you post the output of sysconfig -a

Jgiardino · ‎2019-03-26

Thank you Spindle!

Please excuse my typo as I did mean 8.1, 8.1.2P4 to be exact as you'll see below. I included the output of sysconfig -r as well

> sysconfig -a
NetApp Release 8.1.2P4 7-Mode: Fri Apr 26 19:57:25 PDT 2013
System ID: 0142226023 ; partner ID: 0142223592
System Serial Number: 700000543125
System Rev: B0
System Storage Configuration: Single-Path HA
System ACP Connectivity: Full Connectivity
slot 0: System Board 1665 MHz (110-00133 A4)
Model Name: FAS2040
Part Number: 110-00133
Revision: A4
Serial Number: 8008295
BIOS version: 6.1
Processors: 2
Processor ID: 0x6ec
Microcode Version: 0x55
Processor type: Intel(R) Xeon(R) CPU @ 1.66 GHz
Memory Size: 4096 MB
NVMEM Size: 512 MB of Main Memory Used
CMOS RAM Status: OK
Controller: B
slot 0: Internal BGE 10/100 Ethernet Controller
e0P MAC Address: 00:a0:98:2a:3f:ac (auto-100tx-fd-up)
Device Type: BCM5721
memory mapped I/O base 0xfeaf0000, size 0x10000
memory mapped I/O base 0xfe4e0000, size 0x20000
memory mapped I/O base 0xfe4c0000, size 0x20000
I/O base 0x0000bc00, size 0x20
memory mapped I/O base 0xfe480000, size 0x20000
memory mapped I/O base 0xfe460000, size 0x20000
I/O base 0x0000b800, size 0x20
memory mapped I/O base 0xfe2e0000, size 0x20000
memory mapped I/O base 0xfe2c0000, size 0x20000
I/O base 0x0000ac00, size 0x20
slot 0: Dual 10/100/1000 Ethernet Controller G20
e0a MAC Address: 00:a0:98:2a:3f:b1 (auto-1000t-fd-up)
e0b MAC Address: 00:a0:98:2a:3f:b0 (auto-1000t-fd-up)
e0c MAC Address: 00:a0:98:2a:3f:af (auto-1000t-fd-up)
e0d MAC Address: 00:a0:98:2a:3f:ae (auto-1000t-fd-up)
Device Type: Rev 6
memory mapped I/O base 0xfe280000, size 0x20000
memory mapped I/O base 0xfe260000, size 0x20000
I/O base 0x0000a800, size 0x20
slot 0: ATA/IDE Adapter 0e (0x000001f0)
0e.0 STEC NACF1GM1U-B11 01/17/07 977MB 512B/sect (STI1MMK6 10358141744)
memory-mapped I/O base 0x000001f0, size 0x8
memory-mapped I/O base 0x000003f4, size 0x4
memory-mapped I/O base 0x00000170, size 0x8
memory-mapped I/O base 0x00000374, size 0x4
memory-mapped I/O base 0x0000fc00, size 0x10
memory-mapped I/O base 0000000000, size 0x400
slot 0: Interconnect HBA: Mellanox IB MT25204
GUID: 0x99 LID: 0x5 Remote LID: 0x4
Firmware rev: 1.0.800
Hardware rev: 160
Command rev: 1
Cluster Interconnect Port: 4x
memory mapped I/O base 0xfde00000, size 0x100000
prefetchable memory base 0xfd000000, size 0x800000
slot 0: Fibre Channel Target Host Adapter 0a
(QLogic 2432 (2462) rev. 2, <LINK NOT CONNECTED>)
Firmware rev: 5.5.2
Host Port Addr: 000000
FC Nodename: 50:0a:09:80:88:6a:32:67 (500a0980886a3267)
FC Portname: 50:0a:09:81:88:6a:32:67 (500a0981886a3267)
Connection: No link
Switch Port: Unknown
SFP Vendor Name: FINISAR CORP.
SFP Vendor P/N: FTLF8524P2BNV
SFP Vendor Rev: A
SFP Serial No.: PJC4R3S
SFP Connector: LC
SFP Capabilities: 1, 2, 4 Gbit/Sec
I/O base 0x00009400, size 0x100
memory mapped I/O base 0xfe0f8000, size 0x4000
slot 0: Fibre Channel Target Host Adapter 0b
(QLogic 2432 (2462) rev. 2, <LINK NOT CONNECTED>)
Firmware rev: 5.5.2
Host Port Addr: 000000
FC Nodename: 50:0a:09:80:88:6a:32:67 (500a0980886a3267)
FC Portname: 50:0a:09:82:88:6a:32:67 (500a0982886a3267)
Connection: No link
Switch Port: Unknown
SFP Vendor Name: FINISAR CORP.
SFP Vendor P/N: FTLF8524P2BNV
SFP Vendor Rev: A
SFP Serial No.: PJC4R58
SFP Connector: LC
SFP Capabilities: 1, 2, 4 Gbit/Sec
I/O base 0x00009800, size 0x100
memory mapped I/O base 0xfe0fc000, size 0x4000
slot 0: SAS Host Adapter 0c (LSI Logic 1068E rev. B3, SAS, <UP>)
Firmware rev: 1.31.02.00
Base WWN: 5:00a098:000284c:28
Phy State: [0] Enabled, 3.0 Gb/s
[1] Enabled, 3.0 Gb/s
[2] Enabled, 3.0 Gb/s
[3] Enabled, 3.0 Gb/s
00.0 : NETAPP X298_SMUSK01TSSS NA00 847.5GB 512B/sect (9WK3G6S H)
00.1 : NETAPP X298_WVULC01TSSS NA00 847.5GB 512B/sect (WD-WMAW 31238121)
00.2 : NETAPP X298_SMSKP01TSSS NA00 847.5GB 512B/sect (Z1N36G1 K)
00.3 : NETAPP X298_SMOOS01TSSS NA02 847.5GB 512B/sect (9QJ8Q5P 1)
00.4 : NETAPP X298_SMOOS01TSSS NA02 847.5GB 512B/sect (9QJ8Q2A 7)
00.5 : NETAPP X298_SMSKP01TSSS NA00 847.5GB 512B/sect (Z1N1H0V F)
00.6 : NETAPP X298_SMSKP01TSSS NA00 847.5GB 512B/sect (Z1N1H9S 2)
00.7 : NETAPP X298_SMOOS01TSSS NA02 847.5GB 512B/sect (9QJ8Q1Y X)
00.8 : NETAPP X298_WVULC01TSSS NA00 847.5GB 512B/sect (WD-WMAW 30177018)
00.9 : NETAPP X298_SMSKP01TSSS NA00 847.5GB 512B/sect (Z1N27QR K)
00.10: NETAPP X298_SMSKP01TSSS NA00 847.5GB 512B/sect (Z1N1GXW Q)
00.11: NETAPP X298_WVULC01TSSS NA00 847.5GB 512B/sect (WD-WMAW 30767073)
Shelf 0: ESAS Firmware rev. SAS A: 05 SAS B: 05
slot 0: SAS Host Adapter 0d (LSI Logic 1068E rev. B3, SAS, <UP>)
Firmware rev: 1.31.02.00
Base WWN: 5:00a098:000284c:2c
Phy State: [4] Enabled, 3.0 Gb/s
[5] Enabled, 3.0 Gb/s
[6] Enabled, 3.0 Gb/s
[7] Enabled, 3.0 Gb/s
QSFP Vendor: Molex Inc.
QSFP Part Number: 112-00177+A0
QSFP Type: Copper 2m ID:01
QSFP Serial Number: 308522553
01.0 : NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVJ2TB WA)
01.1 : NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVHR94 RA)
01.2 : NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVJ58B JA)
01.3 : NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVJ58B DA)
01.4 : NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVJ58B 6A)
01.5 : NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVJ50N XA)
01.6 : NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVJ57U 0A)
01.7 : NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVJ56V 3A)
01.8 : NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVJ586 KA)
01.9 : NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVJ4EN UA)
01.10: NETAPP X308_HMARK03TSSM NA04 2538.5GB 512B/sect (YXG2V6 MG)
01.11: NETAPP X308_HMARK03TSSA NA01 2538.5GB 512B/sect (YVJ58D WA)
01.12: NETAPP X308_HMARK03TSSM NA04 2538.5GB 512B/sect (YHH9U7 UA)
01.13: NETAPP X308_HMARK03TSSM NA04 2538.5GB 512B/sect (YHH9U7 VA)
01.14: NETAPP X308_HMARK03TSSM NA04 2538.5GB 512B/sect (YHH9T8 JA)
01.15: NETAPP X308_HMARK03TSSM NA04 2538.5GB 512B/sect (YHH9WL JA)
01.16: NETAPP X308_HMARK03TSSM NA04 2538.5GB 512B/sect (YHH9VK RA)
01.17: NETAPP X308_HMARK03TSSM NA04 2538.5GB 512B/sect (YHH9U6 EA)
01.18: NETAPP X308_HMRKP03TSSA NA01 2538.5GB 512B/sect (P9HS0A DY)
01.19: NETAPP X308_HMRKP03TSSA NA01 2538.5GB 512B/sect (P9HS1M VY)
01.20: NETAPP X308_HMRKP03TSSA NA01 2538.5GB 512B/sect (P9HRMK NY)
01.21: NETAPP X308_HMRKP03TSSA NA01 2538.5GB 512B/sect (P9HS1G 8Y)
01.22: NETAPP X308_HMRKP03TSSA NA01 2538.5GB 512B/sect (P9HRRJ AY)
01.23: NETAPP X308_HMRKP03TSSA NA01 2538.5GB 512B/sect (P9HS4N 8Y)
Shelf 1: IOM3 Firmware rev. IOM3 A: 0160 IOM3 B: 0160
I/O base 0x0000c800, size 0x100
memory mapped I/O base 0xfe9fc000, size 0x4000
memory mapped I/O base 0xfe9e0000, size 0x10000
Baseboard Management Controller:
Firmware Version: 1.3
IPMI version: 2.0
DHCP: off

Gateway IP address: 10.17.1.1
BMC ARP interval: 10 seconds
BMC has (1) user: naroot
ASUP enabled: on
ASUP mailhost: smtp.ogilvy.com
ASUP from: camonetapp01@ogilvy.com
ASUP recipients:
Uptime: 104 Days, 16:31:20
> sysconfig -r
Aggregate aggr_3T (online, raid_dp) (block checksums)
Plex /aggr_3T/plex0 (online, normal, active, pool0)
RAID group /aggr_3T/plex0/rg0 (normal, block checksums)

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity 0d.01.0 0d 1 0 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
parity 0d.01.1 0d 1 1 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.2 0d 1 2 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.3 0d 1 3 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.4 0d 1 4 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.5 0d 1 5 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.6 0d 1 6 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.7 0d 1 7 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.8 0d 1 8 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.10 0d 1 10 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.11 0d 1 11 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.12 0d 1 12 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.13 0d 1 13 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.14 0d 1 14 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816

RAID group /aggr_3T/plex0/rg1 (normal, block checksums)

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
dparity 0d.01.15 0d 1 15 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
parity 0d.01.16 0d 1 16 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.17 0d 1 17 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.18 0d 1 18 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.19 0d 1 19 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.20 0d 1 20 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.21 0d 1 21 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.22 0d 1 22 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816
data 0d.01.23 0d 1 23 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816

Pool1 spare disks (empty)

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 0d.01.9 0d 1 9 SA:A 0 BSAS 7200 2538546/5198943744 2543634/5209362816

Partner disks

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
partner 0c.00.3 0c 0 3 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.7 0c 0 7 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.6 0c 0 6 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.10 0c 0 10 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.9 0c 0 9 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.5 0c 0 5 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.4 0c 0 4 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.2 0c 0 2 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.1 0c 0 1 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.0 0c 0 0 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.8 0c 0 8 SA:B 0 SATA 7200 0/0 847884/1736466816
partner 0c.00.11 0c 0 11 SA:B 0 SATA 7200 0/0 847884/1736466816

SpindleNinja · ‎2019-03-26

Thanks.

Are your aggrs 32bit or 64bit?

p.s. you might want to clean up a bit of the things like IP address and name of the controller if you want.

Jgiardino · ‎2019-03-27

64bit sir. Yeah I realized I left those afterwards and cant seem to edit my post so I'll probably just take it down. Please let me know if you would like anything else. I'll try adding some disk drives to the RG tomorrow to see if that helps.

SpindleNinja · ‎2019-03-27

no prob, just leave things like the ontap version and such. just so it keeps the thread realative for any one else looking at this.

The only other thing I can think of is if you manybe have a 32 bit snapshot still around?
per this: https://library.netapp.com/ecmdocs/ECMLP2346396/html/GUID-207AD86F-E698-4543-A9FE-085F4067466C.html

snap list -fs-block-format

will allow you to check to see what you have there.

RajeshPanda · ‎2019-04-02

@Jgiardino following up to see if you got a chance to look into the recommndetaion provided for your issue, let us know if you are still looking for help.