vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can resize a storage volume after its initial creation. To delete a volume, its status must indicate one of the following states: available, error, error_restoring, error_extending, or error_managing. Additionally, the storage volume cannot be deleted if it is migrating, attached, belongs to a group, has snapshots, or is disassociated from its snapshots after a transfer. Resizing is not immediately available after you deploy a VM. For IBM i 7.3 and later versions, you can resize volume to increase the volume size, but this requires an initial program load (IPL) to recognize the new volume size.

Before you perform the IPL operation, you must run the macro to ensure that the volume resize operation is complete, then proceed with the IPL operation. For more information, see [Dynamically increasing the size of a SAN LUN](https://www.ibm.com/support/pages/dynamically-increasing-size-san-lun). If you perform an IPL operation before the resize operation is complete, an additional IPL is required.

If you cannot take the downtime, you can add additional volumes. You can attach maximum of 127 volumes to the VM.

Any volume that has been included in a snapshot cannot be resized. To resize a volume that has been included in a snapshot, you must first delete all of the snapshots the volume is a part of.



1. Go to the Power Systems Virtual Server user interface and click Storage volumes.
2. Click the Edit icon to the right of your storage volume.
3. Click on Edit to select the desired storage volume size in the Modify storage volume window. You can increase only the size of the storage volume.
4. Read the service agreement and agree to the terms. Click Order to complete the volume modification process and accept the price.
5. To verify your new storage size, go back to Storage volumes.
6. In an AIX VM instance, if you resize your boot storage volume, run the chvg -g rootvg command.
From the Satellite storage dashboard, select the storage configuration you want to delete.
2. Select Actions > Delete
3. Enter the name of your storage configuration.
4. Select Delete.









 Parameter reference 



 21.04 parameter reference 



Table 1. 21.04 parameter reference

 Display name CLI option Type Description Required? Default value 

 Management LIF managementLIF Config The IP address of the Management LIF. true N/A 
 Data LIF dataLIF Config The IP address of the Data LIF. true N/A 
 SVM svm Config The name of the SVM. true N/A 
 User Name username Secret The username to connect to the storage device. true N/A 
 User Password password Secret The password to connect to the storage device. true N/A 
 Export Policy exportPolicy Config The NAS option for the NFS export policy. true default 
 Limit Volume Size limitVolumeSize Config Maximum requestable volume size (in Gibibytes) and qtree parent volume size true 50Gi 
 Limit AggregateUsage limitAggregateUsage Config Fail provisioning if usage is above this percentage. true 80% 
 NFS Mount Options nfsMountOptions Config The NFS mount options. true nfsvers=4 







 22.04 parameter reference 



Table 2. 22.04 parameter reference

 Display name CLI option Type Description Required? Default value 

 Management LIF managementLIF Config The IP address of the Management LIF. true N/A 
 Data LIF dataLIF Config The IP address of the Data LIF. true N/A 
 SVM svm Config The name of the SVM. true N/A 
 User Name username Secret The username to connect to the storage device. true N/A 
 User Password password Secret The password to connect to the storage device. true N/A 
 Export Policy exportPolicy Config The NAS option for the NFS export policy. true default
Resolving the problem 

The largest consumers of storage space are machine learning and rule-based models. To free up space, you can take the following actions:



* Delete snapshot versions of any models that you do not expect to need to revert to.
* Delete any models that you do not need.
* If your models are too important to delete, consider increasing the amount of storage in your deployment.









 Contacting IBM Support 

IBM Support provides assistance with product defects, answers FAQs, and helps users resolve problems with the product.

The developer communities are open to everyone and are a great place to start. For links, see the "Developer community" section at the bottom of the table of contents.

To contact IBM Support:

You must be authorized to create support cases on the IBM Cloud Service Portal.



1. Define the problem, gather background information, and determine the severity of the problem.
2. Gather diagnostic information, if possible.
3. Create a case on the [IBM Cloud Service Portal ![External link icon](https://cloud.ibm.com/docs-content/v1/content/icons/launch-glyph.svg)](https://watson.service-now.com/wcp).
Enter the new storage size in GB.
4. Review your selection and the new pricing.
5. Click Modify.
6. Your new storage allocation is available in a few minutes.



The Operating system must rescan the storage and reload the multipath device map to reflect the expanded volume size. Resizing of the partition and file system are also required. For more information about expanding the file system, see your OS Documentation. For example, [RHEL 8 - Modifying Logical Volume](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_logical_volumes/modifying-the-size-of-a-logical-volume_configuring-and-managing-logical-volumes) or [Microsoft® - Extend a basic volume](https://docs.microsoft.com/en-us/windows-server/storage/disk-management/extend-a-basic-volume).





 Resizing storage from the CLI 

By using the following command, you can increase your volume from the SLCLI.

 slcli block volume-modify --help
Usage: slcli block volume-modify [OPTIONS] VOLUME_ID

Options:
-c, --new-size INTEGER New Size of block volume in GB. If no size
is given, the original size of volume is
used.
Potential Sizes: [20, 40, 80, 100,
250, 500, 1000, 2000, 4000, 8000, 12000]
Minimum: [the original size of the volume]
-i, --new-iops INTEGER Performance Storage IOPS, between 100 and 6000
in multiples of 100 [only for performance
volumes] If no IOPS value is specified, the
original IOPS value of the volume will be
used.
Requirements: [If original IOPS/GB
for the volume is less than 0.3, new IOPS/GB
must also be less than 0.3. If original
IOPS/GB for the volume is greater than or
equal to 0.3, new IOPS/GB for the volume must
Unmount, then mount the modified volume, so the OS can recognize the extra storage space.





 Resizing storage with Terraform 

You can increase your storage capacity by using the ibm_storage_file resource, and specifying a different number in the capacity argument. The following example increases the capacity of an Endurance volume to 40 GB.

resource "ibm_storage_file" "fs_endurance" {
type = "Endurance"
datacenter = "dal09"
capacity = 40
iops = 0.25
}

The following example increases the capacity of a Performance volume to 40 GB.

resource "ibm_storage_file" "fs_performance" {
type = "Performance"
datacenter = "dal09"
capacity = 40
iops = 100
}

For more information about the arguments and attributes, see [ibm_storage_file](https://registry.terraform.io/providers/IBM-Cloud/ibm/latest/docs/resources/storage_file).

Unmount, then mount the modified volume, so the OS can recognize the extra storage space.





 Expanding Storage over 12 TB 

If you need to increase your Storage volume capacity beyond 12 TB, you can request to be added to the allowlist by submitting a [support case](https://cloud.ibm.com/unifiedsupport/cases/add). When the request is approved by the Offering Manager, you're going to be notified through the case process. You're also going to see the option to increase your storage up to 24 TB in the console.

The number of operations that can be performed on the storage is limited. This limit is 180k IOPS. So if you want to provision a volume with 10 IOPS, your maximum volume size is 18 TB. If you want to provision the maximum size of 24 TB, then the maximum rate of reads and writes to the volume is 4 IOPS per GB.
For example, [RHEL 8 - Modifying Logical Volume](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_logical_volumes/modifying-the-size-of-a-logical-volume_configuring-and-managing-logical-volumes) or [Microsoft® - Extend a basic volume](https://docs.microsoft.com/en-us/windows-server/storage/disk-management/extend-a-basic-volume).





 Resizing storage with the API 

You can increase your storage capacity by using an API call to the SOAP web service. The following sample API calls can be called from the scripting language of your choice.

For more information about the SLAPI, see the [SLDN](http://sldn.softlayer.com/reference/softlayerapi).



* Increase capacity on a Performance storage volume.

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://api.service.softlayer.com/soap/v3.1/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<SOAP-ENV:Header>
<ns1:authenticate>
</ns1:authenticate>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<ns1:placeOrder>
You cannot scale down storage. You can recover space by backing up and restoring to a new deployment.





 Memory 

By default, your deployment is configured with a noeviction policy so your memory resources should be scaled to fit your data set. Each data node contains a copy of your data, so the total amount of memory you use is approximately twice the size of your data set. When you add memory to the total allocation, it adds memory to both members equally.

Also, your deployment is configured with maxmemory is set to use 80% of the node's memory, so when scaling up memory to accommodate more data, you might also want to [adjust the maxmemory setting](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-changing-configuration).

If you [configured Redis as a cache](https://cloud.ibm.com/docs/databases-for-redis?topic=databases-for-redis-redis-cache), you can scale to the amount of memory that best fits your caching needs.





 Dedicated Cores 

You can enable or increase the CPU allocation to the deployment. With dedicated cores, your resource group is given a single-tenant host with a reserve of CPU shares. Your deployment is then guaranteed the minimum number of CPUs you specify. The default of 0 dedicated cores uses compute resources on shared hosts.Going from a 0 to a >0 CPU count provisions and moves your deployment to new hosts, and your databases are restarted as part of that move. Going from >0 to a 0 CPU count, moves your deployment to a shared host and also restarts your databases as part of the move.







 Scaling Considerations 



* Scaling your deployment up might cause your databases to restart. If your deployment needs to be moved to a host with more capacity then the databases are restarted as part of the move.
* Scaling down RAM or CPU does not trigger database restarts.
* Disk can not be scaled down.
* A few scaling operations can be more long running than others. Enabling dedicated cores moves your deployment to its own host and can take longer than just adding more cores.
Determine whether you want to reload the existing configuration or reload the device with a new configuration.



Table 1. OS and software reload options

 Reload type Steps 

 If you want to reload a new configuration... Click Edit for the category that requires an update. Select the new software from the Select software drop-down list. 
 If you want to reload the existing configuration... Proceed to the next step. 
 If you want to change the operating system... Click Edit OS > Change version or manufacturer. 



4. Determine whether to apply a postinstallation script after the device is provisioned.

If you want to apply a postinstallation script, select the script from the Existing script drop-down list or enter the qualified URL for the new script. Otherwise, proceed to the next step.
5. For physical devices, determine whether to add or remove installed partitions or if they need to remain unchanged.



Table 2. Partition action options

 Partition action Steps 

 To add installed partitions... Click Add another partition. > Enter the exact name of the partition. > Enter the partition size (in GB). <br>Optionally, you can select Grow to grow the partition to fill the remaining disk space. Keep in mind that you can only one partition can be selected to grow at any time. This partition is larger than the specified size, and fills all available capacity. The capacity of the grow partition is calculated by subtracting the combined size of all other partitions from the total capacity number that is provided in the Installed Partitions section. 
 To delete installed partitions... Click Delete to delete the partition. 
 To remain unchanged... Proceed to the next step. 



6. Determine whether to apply one or more SSH keys to the device.
7. Select the applicable checkboxes for the options that you want to apply to the device during or after the OS reload.

Options vary based on device. Not all options are available for every device.

Postinstallation script Adds an existing or new postinstallation script.
If you want to keep the PV, the physical storage device and your data when you remove the PVC, enter Retain. If you want to delete the PV, the physical storage device and your data when you remove the PVC, enter Delete.

allowVolumeExpansion
: Enter the volume expansion policy for your storage class. If you want to allow volume expansion, enter true. If you don't want to allow volume expansion, enter false.

volumeBindingMode
: Choose if you want to delay the creation of the Block Storage for VPC instance until the first pod that uses this storage is ready to be scheduled. To delay the creation, enter WaitForFirstConsumer. To create the instance when you create the PVC, enter Immediate.
3. Create the customized storage class in your cluster.

kubectl apply -f custom-storageclass.yaml
4. Verify that your storage class is available in the cluster.

kubectl get storageclasses

Example output

NAME PROVISIONER
ibmc-vpc-file-10iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-3iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-5iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-retain-10iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-retain-3iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-retain-5iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-custom vpc.file.csi.ibm.io







 Updating the File Storage for VPC add-on 



1. Disable the add-on.

ibmcloud ks cluster addon disable vpc-file-csi-driver --version VERSION
2. Enable the newer version of the add-on.The add-on might take a few minutes to become ready.
If you want to keep the PV, the physical storage device and your data when you remove the PVC, enter Retain. If you want to delete the PV, the physical storage device and your data when you remove the PVC, enter Delete.

allowVolumeExpansion
: Enter the volume expansion policy for your storage class. If you want to allow volume expansion, enter true. If you don't want to allow volume expansion, enter false.

volumeBindingMode
: Choose if you want to delay the creation of the Block Storage for VPC instance until the first pod that uses this storage is ready to be scheduled. To delay the creation, enter WaitForFirstConsumer. To create the instance when you create the PVC, enter Immediate.
3. Create the customized storage class in your cluster.

oc apply -f custom-storageclass.yaml
4. Verify that your storage class is available in the cluster.

oc get storageclasses

Example output

NAME PROVISIONER
ibmc-vpc-file-10iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-3iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-5iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-retain-10iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-retain-3iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-retain-5iops-tier vpc.file.csi.ibm.io
ibmc-vpc-file-custom vpc.file.csi.ibm.io







 Updating the File Storage for VPC add-on 



1. Disable the add-on.

ibmcloud oc cluster addon disable vpc-file-csi-driver --version VERSION
2. Enable the newer version of the add-on.The add-on might take a few minutes to become ready.
Example:When the currently allocated memory for the logical partition is 4GB and you are trying to reduce the value to 2GB and the logical partition at the time of request does not have free 2GB memory for resizing (considering the logical partition is using upto 3 GB for running resources in it) and can free up only 1 GB, then the partial resize should be possible to reduce the memory to 3GB.

In the current cloud environment, it may take upto 1.5 hours approximately for the change in memory to be updated to places referring to the memory of the logical partition. Hence if you attempt to repeat the resize request, the consecutive retires will fail, until all referencing tables are updated.
This setting is specific to the VMware® datastore and not to the host.





 Configuring Storage I/O Control for Virtual Servers 

You can also limit individual virtual disks for individual VMs or grant them different shares with SIOC. By limiting the disks and granting different shares, you can match and align the environment to the workload with the acquired File Storage for Classic volume IOPS number. The limit is set by IOPS, and it's possible to set a different weight or "Shares." Virtual disks with shares set to High (2,000 shares) receive twice as much I/O as a disk set to Normal (1,000 shares). They receive four times as much IO as one set to Low (500 shares). Normal is the default value for all the VMs, so you need to adjust the values to High or Low for the VMs that require it.

Use the following steps to change the VDisk shares and limit.



1. Choose a Virtual Servers in the VMs and Templates inventory.
2. Select the Virtual Servers for I/O Control.
3. Click the Manage tab and click Settings. Click Edit.
4. Expand the hard disk arrow. Select Modify the Shares or Limit - IOPs as is appropriate for your environment. Choose a virtual hard disk from the list and modify the Shares selection to choose the relative number of shares to allocate to the Virtual Servers (Low, Normal, or High). You can also click Custom and enter a user-defined share value.
5. Click the Limit - IOPS column and enter the maximum storage resources to allocate to the virtual machine.
6. Click OK.



This process is used to set the resource consumption limits of individual vDisks in a Virtual Servers even when SIOC is not enabled. These settings are specific to the individual guest, and not the host, although they are used by SIOC.







 Configuring ESXi host side settings 

Other settings are required for configuring ESXi hosts for NFS storage. This table shows what each setting needs to be.



Table 2 - Host side settings.

 Parameter Set to ...
You can also use the [CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes&interface=cliexpand-existing-boot-vol-cli) or the [API](https://cloud.ibm.com/docs/vpc?topic=vpc-resize-boot-volumes&interface=apiexpand-existing-boot-vol-api).
* How many volumes can I provision on my account?

 How many volumes can I provision on my account? 

You can provision up to 300 Block Storage for VPC volumes per account in a region. You can request your quota to be increased by opening a [support case](https://cloud.ibm.com/unifiedsupport/cases/form) and specifying the region where you need more volumes. For more information about preparing a support case when you're ordering Block Storage for VPC volumes or requesting an increase to your volume or capacity limits, see [Managing volume count and capacity limits](https://cloud.ibm.com/docs/vpc?topic=vpc-manage-storage-limit).
* Can I set up shared storage in a multizone cluster?

 Can I set up shared storage in a multizone cluster? 

In the IBM Cloud®, storage options are limited to an availability zone. Do not try to manage shared storage across multiple zones.

Instead, use an IBM Cloud® classic service option outside a VPC such as IBM Cloud® Object Storage or IBM® Cloudant® for IBM Cloud® if you must share your data across multiple zones and regions.
* I have volumes on the Classic infrastructure. Can I port them to the VPC?

 I have volumes on the Classic infrastructure. Can I port them to the VPC? 

No. The VPC provides access to new availability zones in multi-zone regions. Compute, network, and storage resources are designed to function in the VPC.
* What is image from volume and how does it relate to Block Storage for VPC volumes?

 What is image from volume and how does it relate to Block Storage for VPC volumes?
* UI
* CLI
* API
* Terraform







 Ordering File Storage for Classic 

You can provision File Storage for Classic and fine-tune to meet your capacity and IOPS needs. Get the most out of your storage with two options for specifying performance.



* You can choose from Endurance IOPs tiers that feature pre-defined performance levels to fit workloads that don't have well-defined performance requirements.
* You can fine-tune your storage to meet specific performance requirements by specifying the total number of IOPS with Performance.





 Ordering File Storage for Classic in the UI 



1. Log in to the [IBM Cloud® catalog](https://cloud.ibm.com/catalog) and click Storage. Then, select File Storage for Classic. Click Create.
2. Select your deployment location (region, location, zone).



* Ensure that the new Storage is added in the same location as the compute host or hosts that you have.



3. Billing. If you selected a data center with improved capabilities (marked with an asterisk), you can choose between Monthly or Hourly Billing.



* With hourly billing, the number of hours that the file volume existed on the account is calculated at the time the volume is deleted or at the end of the billing cycle. Which ever comes first. Hourly billing is a good choice for storage that is used for a few days or less than a full month.
* With monthly billing, the calculation for the price is pro-rated from the date of creation to the end of the billing cycle and billed immediately. If a file volume is deleted before the end of the billing cycle, the difference is not refunded. Monthly billing is a good choice for storage that is used in production workloads that use data that needs to be stored and accessed for long periods of time (month or longer).



4. Enter your storage size in the Size field.
5. Select the size of the Snapshot space from the list.

This space is in addition to your usable space.