Changes between Version 3 and Version 4 of Admin/StandardOperatingProcedures/GrowFileSystem


Ignore:
Timestamp:
Jan 1, 2019, 11:26:04 PM (5 years ago)
Author:
Mikael Brandström Durling
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Admin/StandardOperatingProcedures/GrowFileSystem

    v3 v4  
    44
    55==== The my-gridfront case ====
    6 my-gridstore1 is using the Linux iSCSI iitiator to mount iSCSI targets on mykonas4 and reexport these using NFSv4.
    7 1. Log on to mykonas4 and increase the size of the LUN for the iSCSI target used.
    8 1. Log on to my-mgridstore and run ```sudo iscsiadm -m session -R``` to rescan the iSCSI target in order for the system to pick up the increase in volume size.
    9 1. Grow the filesystem by running ```sudo resize2fs /dev/sdX``` where /dev/sdX is replaced with the device corresponding to the filesystem you want to increase the size of. N.B. /export/home1 is not always mounted on /dev/sdc, it varies from boot to boot, check with df or mount. If using multi pathing, they will be found as /dev/mapper/something.
     6my-gridfront is using the Linux iSCSI iitiator to mount iSCSI targets on mykonas6 and reexport these using NFSv4.
     71. Log on to mykonas6 and increase the size of the LUN for the iSCSI target used.
     81. Log on to my-gridfront and run `sudo iscsiadm -m session -R` to rescan the iSCSI target in order for the system to pick up the increase in volume size.
     91. Resize the multiparth device by running `multipathd resize map NNNNNN`
     101. Grow the filesystem by running `sudo resize2fs /dev/mapper/NNNNNN` where /dev/mapper/NNNN is replaced with the device corresponding to the filesystem you want to increase the size of. N.B. /export/home1 is not always mounted on /dev/sdc, it varies from boot to boot, check with df or mount. If using multi pathing, they will be found as /dev/mapper/something.
    1011
    1112