Thank you all for your kind advice.
-- Razvan N. Popescu Research Computing Director Office: (212) 851-9298 [email protected]<mailto:[email protected]> Columbia Business School At the Very Center of Business From: gpfsug-discuss <[email protected]> on behalf of Andrew Beattie <[email protected]> Reply-To: gpfsug main discussion list <[email protected]> Date: Wednesday, June 14, 2023 at 5:57 PM To: gpfsug main discussion list <[email protected]> Subject: Re: [gpfsug-discuss] Increase volume size after nsd/disk creation Razvan, We do not support increasing the size of an existing NSD. As mentioned earlier you need to add new NSD, of the new size you require, and then remove the old NSD resize to the new size and then add the new NSD back to the filesystem. When you have added all the new NSD to the filesystem (you need to make sure they are all the same size - or you will end up with performance degradation) then you need to run a mmrestripe accross thr filesystem to rebalance the data and metadata appropriately. Regards, Andrew Beattie Technical Sales Specialist - Storage for Big Data & AI IBM Australia and New Zealand P. +61 421 337 927 E. [email protected] Twitter: AndrewJBeattie LinkedIn: ________________________________ From: gpfsug-discuss <[email protected]> on behalf of Alec <[email protected]> Sent: Thursday, June 15, 2023 6:00:32 AM To: gpfsug main discussion list <[email protected]> Subject: [EXTERNAL] Re: [gpfsug-discuss] Increase volume size after nsd/disk creation perhaps mmnsddiscover will do it for you, I guess not though. . . You should be able at the worst case increase the disk size, then do a mmdeldisk and an mmadddisk to reimport each disk at the new size. If memory serves though the meta size is ZjQcmQRYFpfptBannerStart This Message Is From an External Sender This message came from outside your organization. <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/PjiDSg!12-vrJCURtUSUMnXsIvq4BYyoVaWW77CHMdL1gW-WaUgrcb1bfSzXNMxf-CN38JJs4s_2lmgBX_gvjIlhgD4RRpbw88xEZNhGLcVbBb_pX8pZuIy4hM278OfgtcW$> Report Suspicious <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/PjiDSg!12-vrJCURtUSUMnXsIvq4BYyoVaWW77CHMdL1gW-WaUgrcb1bfSzXNMxf-CN38JJs4s_2lmgBX_gvjIlhgD4RRpbw88xEZNhGLcVbBb_pX8pZuIy4hM278OfgtcW$> ZjQcmQRYFpfptBannerEnd perhaps mmnsddiscover will do it for you, I guess not though... You should be able at the worst case increase the disk size, then do a mmdeldisk and an mmadddisk to reimport each disk at the new size. If memory serves though the meta size is based on the size of the first disk that is imported and won't increase, which affects how large your pool can actually grow to. I'm sure there are workarounds to that though. Alec On Wed, Jun 14, 2023, 12:42 PM Popescu, Razvan <[email protected]<mailto:[email protected]>> wrote: Hello, Does anyone know if GPFS allows the increase in capacity of already existing nsd/disks, in order to add capacity to a storage pool? I need to increase the space on an existing filesystem, and wonder if rather than having to add new nds/disks to the storage pool, I could leverage the ability of the backend block storage array (NetApp E5600) to increase the capacity of existing raid volumes, and propagate the increase in space all the way through nsd/disk/storage pool. Sounds somewhat close to handling thin disks – yes, not quite the same, but I found no reference in the manuals either way. Many thanks! Razvan Columbia Business School At the Very Center of Business _______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at gpfsug.org<http://gpfsug.org> http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
_______________________________________________ gpfsug-discuss mailing list gpfsug-discuss at gpfsug.org http://gpfsug.org/mailman/listinfo/gpfsug-discuss_gpfsug.org
