Subscribe

NetApp FAS3140 LUN RESIZE, help me please!

LUN STATUS

fas3140b> df -g

Filesystem               total       used      avail capacity  Mounted on                                                                        apshot

/vol/voluat/             400GB      300GB       99GB      75%  /vol/voluat/

/vol/voluat/.snapshot        0GB        0GB        0GB     ---%  /vol/voluat/.sn                                                                              apshot

fas3140b> lun show -v

        /vol/voluat/qt1/lunuat     300.0g (322163441664)  (r/w, online, mapped)

                Serial#: W-Q7c4Y9UT5r

                Share: none

                Space Reservation: enabled

                Multiprotocol Type: aix

                Maps: uat_igroup=2

lun is currently empty 300GB 100GB, I would like to increase to 350GB lun


LUN RESIZE STATUS

fas3140b> lun resize /vol/voluat/qt1/lunuat.lun +50g

lun resize: No such LUN exists

fas3140b> lun resize /vol/voluat/qt1/lunuat +50g

lun resize: resized to:  350.1g (375881990144)

successful implementation resize lun

fas3140b> lun show -v /vol/voluat/qt1/lunuat

        /vol/voluat/qt1/lunuat     350.1g (375881990144)  (r/w, online, mapped)

                Serial#: W-Q7c4Y9UT5r

                Share: none

                Space Reservation: enabled

                Multiprotocol Type: aix

                Maps: uat_igroup=2

fas3140b> df -g

Filesystem               total       used      avail capacity  Mounted on

/vol/voluat/             400GB      350GB       49GB      88%  /vol/voluat/

/vol/voluat/.snapshot        0GB        0GB        0GB     ---%  /vol/voluat/.snapshot

But I do not see IBM power capacity to increase hdisk map

[root@uat:/]# lspv -L hdisk2

PHYSICAL VOLUME:    hdisk2                   VOLUME GROUP:     uatdatavg

PV IDENTIFIER:      00c713a535ed94bd VG IDENTIFIER     00c713a500004c000000012a6e893410

PV STATE:           active                                    

STALE PARTITIONS:   0                        ALLOCATABLE:      yes

PP SIZE:            512 megabyte(s)          LOGICAL VOLUMES:  2

TOTAL PPs:          600 (307200 megabytes)   VG DESCRIPTORS:   2

FREE PPs:           0 (0 megabytes)          HOT SPARE:        no

USED PPs:           600 (307200 megabytes)   MAX REQUEST:      256 kilobytes

FREE DISTRIBUTION:  00..00..00..00..00                        

USED DISTRIBUTION:  120..120..120..120..120                   

MIRROR POOL:        None                   

[root@uat:/]# lsvg

rootvg

uatdatavg

[root@uat:/]# lsvg uatdatavg

VOLUME GROUP:       uatdatavg                VG IDENTIFIER:  00c713a500004c000000012a6e893410

VG STATE:           active                   PP SIZE:        512 megabyte(s)

VG PERMISSION:      read/write               TOTAL PPs:      600 (307200 megabytes)

MAX LVs:            512                      FREE PPs:       0 (0 megabytes)

LVs:                2                        USED PPs:       600 (307200 megabytes)

OPEN LVs:           2                        QUORUM:         2 (Enabled)

TOTAL PVs:          1                        VG DESCRIPTORS: 2

STALE PVs:          0                        STALE PPs:      0

ACTIVE PVs:         1                        AUTO ON:        yes

MAX PPs per VG:     130048                                   

MAX PPs per PV:     1016                     MAX PVs:        128

LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no

HOT SPARE:          no                       BB POLICY:      relocatable

[root@uat:/]# lsvg uatdatavg

VOLUME GROUP:       uatdatavg                VG IDENTIFIER:  00c713a500004c000000012a6e893410

VG STATE:           active                   PP SIZE:        512 megabyte(s)

VG PERMISSION:      read/write               TOTAL PPs:      600 (307200 megabytes)

MAX LVs:            512                      FREE PPs:       0 (0 megabytes)

LVs:                2                        USED PPs:       600 (307200 megabytes)

OPEN LVs:           2                        QUORUM:         2 (Enabled)

TOTAL PVs:          1                        VG DESCRIPTORS: 2

STALE PVs:          0                        STALE PPs:      0

ACTIVE PVs:         1                        AUTO ON:        yes

MAX PPs per VG:     130048                                   

MAX PPs per PV:     1016                     MAX PVs:        128

LTG size (Dynamic): 256 kilobyte(s)          AUTO SYNC:      no

HOT SPARE:          no                       BB POLICY:      relocatable

Please help me!

thanks all

Re: NetApp FAS3140 LUN RESIZE, help me please!

Hi,

Once you've changed LUN size on storage side, you need to make you host OS aware about that. I'm not familiar with AIX, but here is CentOS / RHEL 5.5 example (assuming that the LUN is known as /dev/sda device on the host):

echo 1 > /sys/block/sda/device/rescan

It will make the host OS aware about the LUN size changed.

Real life configurations are usually more complicated than that and invoke "volume managers", so you'd need to make extra steps to make your volume manager aware about storage side changes.

Vladimir

Re: NetApp FAS3140 LUN RESIZE,  help me please!

I still do not do it, anyone know this problem with help

Re: NetApp FAS3140 LUN RESIZE,  help me please!

This looks like a support related issue.  If this is critical, you should open a case with NetApp Support.  If it is not a critical issue, we have external and internal subject matter experts in the NetApp Support Community answering questions about Filers.  If you have an active NetApp Single Sign On (SSO) account login, this link enables you to engage them about this.