<html><body><p><font size="2">Option 'suspend' is same to 'empty' if the cluster is updated to Scale 4.1.1. The option 'empty' was introduced in 4.1.1 to support disk deletion in a fast way, 'suspend' option was not removed with due consideration for previous users.</font><br><br><tt><font size="2">> And really what I currently want to do is suspend a set of disks, <br>> and then mark a different set of disks as ¡°to be emptied¡±. Then I <br>> will run a mmrestripefs operation to move the data off of the ¡°to be<br>> emptied¡± disks, but not onto the suspended disks (which will also be<br>> removed from the file system in the near future). Once the NSDs are<br>> emptied then it will be a very (relatively) fast mmdeldisk <br>> operation. So is that possible?</font></tt><br><br><font size="2">It's possible only if these two sets of disks belong to two different </font><b><font size="2">pools</font></b><font size="2">.</font><br><br><font size="2">If they are in the same pool, restripefs on the pool will migrate all data off these two sets of disks.</font><br><br><font size="2">If they are in two different pools, you can use mmrestripefs with -P option to migrate data off "suspended" and "to be emptied" disks in the specified data pool. Please note that system pool is special, mmrestripefs will unconditionally restripe the system pool even you specified -P option to a data pool.</font><br><br><br><font size="2">Regards, The Spectrum Scale (GPFS) team<br><br>------------------------------------------------------------------------------------------------------------------<br>If you feel that your question can benefit other users of Spectrum Scale (GPFS), then please post it to the public IBM developerWroks Forum at <a href="https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479">https://www.ibm.com/developerworks/community/forums/html/forum?id=11111111-0000-0000-0000-000000000479</a>. <br><br>If your query concerns a potential software error in Spectrum Scale (GPFS) and you have an IBM software maintenance contract please contact 1-800-237-5511 in the United States or your local IBM Service Center in other countries. <br><br>The forum is informally monitored as time permits and should not be used for priority messages to the Spectrum Scale (GPFS) team.</font><br><br><tt><font size="2">gpfsug-discuss-bounces@spectrumscale.org wrote on 2020/04/23 06:34:33:<br><br>> From: Bryan Banister <bbanister@jumptrading.com></font></tt><br><tt><font size="2">> To: gpfsug main discussion list <gpfsug-discuss@spectrumscale.org></font></tt><br><tt><font size="2">> Date: 2020/04/23 06:35</font></tt><br><tt><font size="2">> Subject: [EXTERNAL] [gpfsug-discuss] Is there a difference in <br>> suspend and empty NSD state?</font></tt><br><tt><font size="2">> Sent by: gpfsug-discuss-bounces@spectrumscale.org</font></tt><br><tt><font size="2">> <br>> Hello all,</font></tt><br><tt><font size="2">> </font></tt><br><tt><font size="2">> Looking at the man page, it is fairly ambiguous as to these NSD <br>> states actually being different (and if not WHY have to names for <br>> the same thing?!):</font></tt><br><tt><font size="2">> </font></tt><br><tt><font size="2">> suspend</font></tt><br><tt><font size="2">> or</font></tt><br><tt><font size="2">> empty</font></tt><br><tt><font size="2">> Instructs GPFS to stop allocating space on the specified</font></tt><br><tt><font size="2">> disk. Put a disk in this state when you are preparing to</font></tt><br><tt><font size="2">> remove the file system data from the disk or if you want</font></tt><br><tt><font size="2">> to prevent new data from being put on the disk. This is</font></tt><br><tt><font size="2">> a user-initiated state that GPFS never enters without an</font></tt><br><tt><font size="2">> explicit command to change the disk state. Existing data</font></tt><br><tt><font size="2">> on a suspended disk may still be read or updated.</font></tt><br><tt><font size="2">> </font></tt><br><tt><font size="2">> A disk remains in a suspended or to be</font></tt><br><tt><font size="2">> emptied state until it is explicitly resumed.</font></tt><br><tt><font size="2">> Restarting GPFS or rebooting nodes does not restore</font></tt><br><tt><font size="2">> normal access to a suspended disk.</font></tt><br><tt><font size="2">> </font></tt><br><tt><font size="2">> And from the examples lower in the page:</font></tt><br><tt><font size="2">> Note: In product versions earlier than V4.1.1, the</font></tt><br><tt><font size="2">> mmlsdisk command lists the disk status as</font></tt><br><tt><font size="2">> suspended. In product versions V4.1.1 and later, the</font></tt><br><tt><font size="2">> mmlsdisk command lists the disk status as to be</font></tt><br><tt><font size="2">> emptied with both mmchdisk suspend or mmchdisk</font></tt><br><tt><font size="2">> empty commands.</font></tt><br><tt><font size="2">> </font></tt><br><tt><font size="2">> </font></tt><br><tt><font size="2">> And really what I currently want to do is suspend a set of disks, <br>> and then mark a different set of disks as ¡°to be emptied¡±. Then I <br>> will run a mmrestripefs operation to move the data off of the ¡°to be<br>> emptied¡± disks, but not onto the suspended disks (which will also be<br>> removed from the file system in the near future). Once the NSDs are<br>> emptied then it will be a very (relatively) fast mmdeldisk <br>> operation. So is that possible?</font></tt><br><tt><font size="2">> </font></tt><br><tt><font size="2">> As you can likely tell, I don¡¯t have enough space to just delete <br>> both sets of disks at once during a (yay!) full file system <br>> migration to the new GPFS 5.x version.</font></tt><br><tt><font size="2">> </font></tt><br><tt><font size="2">> Thought this might be useful to others, so posted here. Thanks in <br>> advance neighbors!</font></tt><br><tt><font size="2">> -Bryan_______________________________________________<br>> gpfsug-discuss mailing list<br>> gpfsug-discuss at spectrumscale.org<br>> <a href="INVALID URI REMOVED">INVALID URI REMOVED</a><br>> u=http-3A__gpfsug.org_mailman_listinfo_gpfsug-2Ddiscuss&d=DwICAg&c=jf_iaSHvJObTbx-<br>> siA1ZOg&r=IbxtjdkPAM2Sbon4Lbbi4w&m=QxEYrybXOI6xpUEVxZumWQYDMDbDLx4O4vrm0PNotMw&s=4M2-<br>> uNMOrvL7kEQu_UmL5VvnkKfPL-EpSapVGkSX1jc&e= <br></font></tt><BR>
</body></html>