vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Create a volume attachment, connecting a volume to an instance.

ibmcloud is instance-volume-attachment-add NAME INSTANCE (VOLUME | --profile PROFILE --new-volume-name NEW_VOLUME_NAME --iops IOPS --encryption-key ENCRYPTION_KEY --capacity CAPACITY --tags TAGS --source-snapshot SOURCE_SNAPSHOT) [--auto-delete false | true] [--output JSON] [-q, --quiet]



 Command examples 



* ibmcloud is instance-volume-attachment-add data-vol-name 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 1a6b7274-678d-4dfb-8981-c71dd9d4daa5
* ibmcloud is instance-volume-attachment-add data-vol-name 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 1a6b7274-678d-4dfb-8981-c71dd9d4daa5 --auto-delete true
* ibmcloud is instance-volume-attachment-add data-vol-name 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 1a6b7274-678d-4dfb-8981-c71dd9d4daa5 --auto-delete true --output JSON
* ibmcloud is instance-volume-attachment-add data-vol-name 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479 --profile general-purpose --source-snapshot eaf9d6ca-35bf-4ac7-bc45-d0f2507f2830 --auto-delete true --output JSON
ibmcloud ks storage attachment create --cluster aa1111aa11aaaaa11aa1 --volume 111111111 --worker kube-aa1111aa11aaaaa11aa1-my_cluster-default-00000110 [--output json]





 ibmcloud ks storage attachment get 

Virtual Private Cloud

Get the details of a storage volume attachment in your cluster.

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

ibmcloud ks storage attachment get --cluster CLUSTER_ID --attachment ATTACHMENT --worker WORKER [--output json]

--cluster CLUSTER_ID
: Required: Specify the cluster ID. To list available clusters, run ibmcloud ks cluster ls.

--attachment ATTACHMENT
: Required: Specify the volume attachment ID. To list available attachments, run ibmcloud ks storage attachment ls.

--worker WORKER
: Required: Specify the worker ID. To list available workers, run ibmcloud ks worker ls.

--output json
: Optional: Prints the command output in JSON format.

Example:

ibmcloud ks storage attachment get --cluster aa1111aa11aaaaa11aa1 --attachment 0111-1a111aaa-1111-1111-111a-aaa1a1a11a11 --worker kube-aa1111aa11aaaaa11aa1-my_cluster-default-00000110 [--output json]





 ibmcloud ks storage attachment ls 

Virtual Private Cloud

List the storage volume attachments for a worker node in your cluster.

Minimum required permissions
: Viewer platform access role for the cluster in IBM Cloud Kubernetes Service

ibmcloud ks storage attachment ls --cluster CLUSTER_ID --worker WORKER [--output json]

--cluster CLUSTER_ID
: Required: Specify the cluster ID. To list available clusters, run ibmcloud ks cluster ls.

--worker WORKER
: Required: Specify the worker ID. To list available workers, run ibmcloud ks worker ls.
* [Replica sets](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appsreplicaset)
* [Labels](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appslabel)
* [Affinity](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appsaffinity)
* [Image policies](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appsimage)
* [Ports](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appsport)
* [Resource requests and limits](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appsresourcereq)
* [Liveness and readiness probes](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appsprobe)
* [Services](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appsapp-service) to expose the app service on a port.
* [Configmaps](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appsconfigmap) to set container environment variables.
* [Secrets](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appssecret) to set container environment variables.
* [Persistent volumes](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_appspv) that are mounted to the container for storage.







 How can I add IBM services to my app, such as Watson?
* [Setting a maximum number of large client header buffers](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationslarge-client-header-buffers)
* [Modifying how the ALB matches the request URI](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationslocation-modifier)
* [Adding custom location block configurations](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationslocation-snippets)
* [Configuring mutual authentication](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsmutual-authentication)
* [Configuring proxy buffer size](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsproxy-buffer-size)
* [Configuring proxy buffer numbers](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsconfig-proxy-buffers)
* [Configuring busy proxy buffer size](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsproxy-busy-buffer-size)
* [Configuring when an ALB can pass a request](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsproxy-next-upstream)
* [Rate limiting](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsrate-limiting)
* [Removing the response header](https://cloud.ibm.com/docs/containers?topic=containers-comm-ingress-annotationsresponse-header-removal)
A successful response looks like the following example.

{
"capacity": 50,
"created_at": "2022-04-22T23:16:53.000Z",
"crn": "crn:[...]",
"encryption": "user_managed",
"encryption_key": {
"crn": "crn:[...]"
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/volumes/2d1bb5a8-40a8-447a-acf7-0eadc8aeb054",
"id": "2d1bb5a8-40a8-447a-acf7-0eadc8aeb054",
"iops": 100,
"name": "my-volume-4-update",
"profile": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/volume/profiles/custom",
"name": "custom"
},
"resource_group": {
"href": "https://resource-controller.cloud.ibm.com/v2/resource_groups/4bbce614c13444cd8fc5e7e878ef8e21",
"id": "4bbce614c13444cd8fc5e7e878ef8e21",
"name": "Default"
},
"status": "available",
"status_reasons": [],
"volume_attachments": [],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-2",
"name": "us-south-2"
}
}





 Updating a volume attachment with the API
x-amz-request-id: 9f39ff2e-55d1-461b-a6f1-2d0b75138861
Content-Type: application/xml
Content-Length: 604

<ListBucketResult xmlns="http://s3.amazonaws.com/doc/2006-03-01/">
<Name>apiary</Name>
<Prefix/>
<ContinuationToken>1dPe45g5uuxjyASPegLq80sQsZKL5OB2by4Iz_7YGR5NjiOENBPZXqvKJN6_PgKGVzZYTlws7qqdWaMklzb8HX2iDxxl72ane3rUFQrvNMeIih49MZ4APUjrAuYI83KxSMmfKHGZyKallFkD5N6PwKg</ContinuationToken>
<NextContinuationToken>1a8j20CqowRrM4epIQ7fTBuyPZWZUeA8Epog16wYu9KhAPNoYkWQYhGURsIQbll1lP7c-OO-V5Vyzu6mogiakC4NSwlK4LyRDdHQgY-yPH4wMB76MfQR61VyxI4TJLxIWTPSZA0nmQQWcuV2mE4jiDA</NextContinuationToken>
<KeyCount>1</KeyCount>
<MaxKeys>1</MaxKeys>
<Delimiter/>
<IsTruncated>true</IsTruncated>
<Contents>
<Key>soldier-bee</Key>
<LastModified>2016-08-25T17:49:06.006Z</LastModified>
<ETag>"37d4c94839ee181a2224d6242176c4b5"</ETag>
<Size>11</Size>
<StorageClass>STANDARD</StorageClass>
</Contents>
"status_reasons": [],
"volume_attachments": [],
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-2",
"name": "us-south-2"
}
}





 Updating a volume attachment with the API 

Make a PATCH /instances call and specify the ID of the new volume attachment.

PATCH /instances/{instance_id}/volume_attachments/{id}

curl -X PATCH "$vpc_api_endpoint/v1/instances/$instance_id/volume_attachments/$volume_attachment_id?version=2022-04-22&generation=2" -H "Authorization: $iam_token" -d '{
"delete_volume_on_instance_delete": false,
"name": "my-volume-attachment-data-5iops-updated"
}'

A successful response looks like the following example.

{
"created_at": "2022-04-22T16:35:47.000Z",
"delete_volume_on_instance_delete": false,
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/8f06378c-ed0e-481e-b98c-9a6dfbee1ed5/volume_attachments/9f2a645e-19c1-4f8f-b062-46b9e0671999",
"id": "9f2a645e-19c1-4f8f-b062-46b9e0671999",
"name": "my-volume-attachment-data-5iops-updated",
"status": "attached",
"type": "data",
"volume": {
"crn": "crn:[...]
fsf-tok0551b-fz.adn.networklayer.com:/ec39996c_346a_4815_a74f_4048382e6ecc/BHB/mnt00002 /hana/data/BHB/mnt00002 nfs sec=sys,rw,vers=4,minorversion=1,hard,timeo=600,rsize=65536,wsize=65536,intr,noatime,lock 0 0
3. /hana/log

fsf-tok0551b-fz.adn.networklayer.com:/7bdee46e_b95f_4ff7_89b8_5273e8f9199d/BHB/mnt00001 /hana/log/BHB/mnt00001 nfs sec=sys,rw,vers=4,minorversion=1,hard,timeo=600,rsize=65536,wsize=65536,intr,noatime,lock 0 0
fsf-tok0551b-fz.adn.networklayer.com:/2bca0419_3aef_40ca_b38f_8b9717c93905/BHB/mnt00002 /hana/log/BHB/mnt00002 nfs sec=sys,rw,vers=4,minorversion=1,hard,timeo=600,rsize=65536,wsize=65536,intr,noatime,lock 0 0



You cannot follow NetApp's recommendation regarding rsize and wsize option, these parameters are limited to 65536 by the file share implementation.
encoding-type String If unicode characters that are not supported by XML are used in an object name, this parameter can be set to url to properly encode the response. 
 max-uploads integer Restricts the number of objects to display in the response. Default and maximum is 1,000. 
 key-marker String Specifies from where the listing should begin. 
 upload-id-marker String Ignored if key-marker is not specified, otherwise sets a point at which to begin listing parts above upload-id-marker. 



Example request

This is an example of retrieving all current canceled and incomplete multipart uploads.

GET /apiary?uploads= HTTP/1.1
Authorization: Bearer {token}
Host: s3.us.cloud-object-storage.appdomain.cloud

Example request

GET /apiary?uploads= HTTP/1.1
Authorization: 'AWS4-HMAC-SHA256 Credential={access-key}/{date}/{region}/s3/aws4_request,SignedHeaders=host;x-amz-date;,Signature={signature}'
x-amz-date: {timestamp}
Content-Type: text/plain
Host: s3.us.cloud-object-storage.appdomain.cloud

Example response (no multipart uploads in progress)

HTTP/1.1 200 OK
Date: Wed, 5 Oct 2016 15:22:27 GMT
X-Clv-Request-Id: 9fa96daa-9f37-42ee-ab79-0bcda049c671
Accept-Ranges: bytes
Server: Cleversafe/3.9.0.129
X-Clv-S3-Version: 2.5
x-amz-request-id: 9fa96daa-9f37-42ee-ab79-0bcda049c671
Content-Type: application/xml
Content-Length: 374
The service supports [XLIFF version 1.2](http://docs.oasis-open.org/xliff/v1.2/os/xliff-core.html). Submit files to the service either with the file extension .xliff or a content-type of application/xliff+xml. The service interprets only the part of XLIFF that can be used to encode aligned text segments. You must ensure that your data has a structure like the following example:

<xliff version='1.2' xmlns='urn:oasis:names:tc:xliff:document:1.2'>
<file original='original.txt' source-language='en' target-language='es' datatype='plaintext'>
<body>
<group>
<trans-unit id='sentence1'>
<source>Hello World</source>
<target>Hola mundo</target>
</trans-unit>
. . .
</group>
</body>
</file>
</xliff>

You must escape the reserved XML control characters &, <, and > with equivalent XML entities. For more information, see [Escaping XML control characters](https://cloud.ibm.com/docs/language-translator?topic=language-translator-customizingtmx-xml-characters).





 CSV 

The service supports comma-separated values (CSV) files that follow the [RFC 4180 specification](https://tools.ietf.org/html/rfc4180). Submit files to the service with either the file extension .csv or a content-type of text/csv. You must structure the CSV file as follows:



* The first row must have two language codes. The first column is for the source language code, and the second column is for the target language code.
* All subsequent rows must have translation pairs, and each row must have two columns. The first column is for the source sentence, and the second column is for the translated sentence.
Contains more than 2100 characters, total www1.example.com www2.example.com www3.example.com www4.example.com www5.example.com... 
 Contains at least one URL match term that has greater than 255 characters www1.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.example.com www.example.org 
 Contains duplicates in the list domain1.example.com domain1.example.com 
 Using characters not specified in [RFC-3986](https://tools.ietf.org/html/rfc3986section-2) domain1.exa}mple.com domain1.example.com 
 A refererValues string with at least one URL match term that has a character set in front of the first . character that contains :// is not supported www.example.org http://www.example.com 
 {: caption="Table 1. Examples of an invalid string for refererValues" caption-side="bottom"}
- --v=5
- --csi-address=/csi/csi.sock
- --timeout=900s
image: quay.io/k8scsi/csi-attacher:v2.2.0
securityContext:
privileged: false
allowPrivilegeEscalation: false
imagePullPolicy: Always
name: csi-attacher
resources:
limits:
cpu: 100m
memory: 100Mi
requests:
cpu: 10m
memory: 20Mi
volumeMounts:
- mountPath: /csi
name: socket-dir
- args:
- --csi-address=/csi/csi.sock
image: quay.io/k8scsi/livenessprobe:v2.0.0
name: liveness-probe
securityContext:
privileged: false
allowPrivilegeEscalation: false
resources:
limits:
cpu: 50m
memory: 50Mi
requests:
cpu: 5m
memory: 10Mi
volumeMounts:
- mountPath: /csi
name: socket-dir
- args:
- --v=5
- --endpoint=$(CSI_ENDPOINT)
- --lock_enabled=false
env:
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
envFrom:
- configMapRef:
name: ibm-vpc-block-csi-configmap
image: icr.io/ibm/ibm-vpc-block-csi-driver:v3.0.0
imagePullPolicy: Always
securityContext:
privileged: false
allowPrivilegeEscalation: false
livenessProbe:
failureThreshold: 5
httpGet:
path: /healthz
05:58:13.474685 IP 166.9.12.121.filenet-nch > 10.171.52.151.33666: Flags [S.], seq 2264270242, ack 2853445050, win 28960, options [mss 1460,sackOK,TS val 1156479729 ecr 592612262,nop,wscale 9], length 0
05:58:13.474718 IP 10.171.52.151.33666 > 166.9.12.121.filenet-nch: Flags [.], ack 1, win 229, options [nop,nop,TS val 592612265 ecr 1156479729], length 0
05:58:13.474806 IP 10.171.52.151.33666 > 166.9.12.121.filenet-nch: Flags [P.], seq 1:115, ack 1, win 229, options [nop,nop,TS val 592612265 ecr 1156479729], length 114
05:58:13.476559 IP 166.9.12.121.filenet-nch > 10.171.52.151.33666: Flags [.], ack 115, win 57, options [nop,nop,TS val 1156479729 ecr 592612265], length 0
05:58:13.583080 IP 166.9.12.121.filenet-nch > 10.171.52.151.33666: Flags [P.], seq 1:145, ack 115, win 57, options [nop,nop,TS val 1156479756 ecr 592612265], length 144
05:58:13.583132 IP 10.171.52.151.33666 > 166.9.12.121.filenet-nch: Flags [.], ack 145, win 237, options [nop,nop,TS val 592612373 ecr 1156479756], length 0
/instance/network_interfaces/{id} port_speed The network interface port speed in Mbps. 
 /instance/network_interfaces/{id} primary_ipv4_address The primary IPv4 address. 
 /instance/network_interfaces/{id} resource_type The resource type. 
 /instance/network_interfaces/{id} security_groups A list of security groups. 
 /instance/network_interfaces/{id} status The status of the network interface. 
 /instance/network_interfaces/{id} subnet The subnet associated with the instance. 
 /instance/network_interfaces/{id} type The type of this network interface as it relates to an instance. 
 /instance/volume_attachments/{id} bandwidth The maximum bandwidth in megabits per second for the volume when attached to this instance. This might be lower than the volume bandwidth depending on the configuration of the instance. 
 /instance/volume_attachments/{id} created_at The date and time that the volume was attached. 
 /instance/volume_attachments/{id} delete_volume_on_instance_delete If set to true, then when you delete the instance, the volume is also deleted. 
 /instance/volume_attachments/{id} device Information about how the volume is exposed to the instance operating system. 
 /instance/volume_attachments/{id} id The unique identifier for the volume attachment. 
 /instance/volume_attachments/{id} name The user-defined name for the volume attachment. 
 /instance/volume_attachments/{id} status The status of the volume attachment: attached, attaching, deleting, or detaching. 
 /instance/volume_attachments/{id} type The type of volume attachment, boot or data. 
 /instance/volume_attachments/{id} volume The attached volume, which contains the CRN, ID, name, and deleted value, when the volume is deleted. 







 Summary of metadata for SSH keys 

Use the information in the Table 2 to understand the type of metadata returned for SSH keys.



Table 2. Metadata for SSH keys

 SSH Key URI path Metadata key Description of the metadata
"name": "boot-volume-1"
}
},
{
"id": "e77125cb-4df0-4988-a878-531ae0ae0b70",
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/e402fa1b-96f6-
4aa2-a8d7-703aac843651/volume_attachments/7389-e77125cb-4df0-4988-a878-
531ae0ae0b70",
"name": "volume-attachment",
"volume": {
"id": "2cc091f5-4d46-48f3-99b7-3527ae3f4392",
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/volumes/2cc091f5-4d46-
48f3-99b7-3527ae3f4392",
"name": "my-volume-2"
}
},
{
"id": "a7641494-5724-46de-9c72-c6b16971ddf4",
"href": "https://us-south.iaas.cloud.ibm.com/v1/instances/e402fa1b-96f6-
4aa2-a8d7-703aac843651/volume_attachments/a7641494-5724-46de-9c72-
c6b16971ddf4",
"name": "volume-attachment",
"volume": {
memory: 20Mi
volumeMounts:
- mountPath: /csi
name: socket-dir
- args:
- --v=5
- --csi-address=/csi/csi.sock
- --timeout=900s
image: quay.io/k8scsi/csi-attacher:v2.2.0
securityContext:
privileged: false
allowPrivilegeEscalation: false
imagePullPolicy: Always
name: csi-attacher
resources:
limits:
cpu: 100m
memory: 100Mi
requests:
cpu: 10m
memory: 20Mi
volumeMounts:
- mountPath: /csi
name: socket-dir
- args:
- --csi-address=/csi/csi.sock
image: quay.io/k8scsi/livenessprobe:v2.0.0
name: liveness-probe
securityContext:
privileged: false
allowPrivilegeEscalation: false
resources:
limits:
cpu: 50m
memory: 50Mi
requests:
cpu: 5m
memory: 10Mi
volumeMounts:
- mountPath: /csi
name: socket-dir
- args:
- --v=5
- --endpoint=$(CSI_ENDPOINT)
- --lock_enabled=false
env:
- name: POD_NAME
valueFrom:
fieldRef:
fieldPath: metadata.name
- name: POD_NAMESPACE
valueFrom:
fieldRef:
fieldPath: metadata.namespace
envFrom:
- configMapRef:
name: ibm-vpc-block-csi-configmap
image: icr.io/ibm/ibm-vpc-block-csi-driver:v3.0.0
imagePullPolicy: Always
securityContext:
privileged: false
r014-f0e809bf-9afb-4006-b2a8-274f81f0f34e concurrent-vol-8xif5f1tid0 unusable 20 3000 general-purpose unattached - us-east-1 defaults
r014-b8e23307-e93e-4f7b-918f-7b2c2b14b132 concurrent-vol-gpwucqfpni0 available 20 3000 general-purpose attached data us-east-1 defaults
r014-a64beeee-be50-4c03-8cee-639106cea1e2 concurrent-vol-mh16478vln0 available 20 3000 general-purpose attached data us-east-1 defaults
r014-f14f8d39-2cf3-4f5d-b366-1d234f1c74aa concurrent-vol-n7fcoxmb860 available 20 3000 general-purpose attached data us-east-1 defaults
r014-84ff8138-4f4f-434b-bdc3-45d1aaaa4329 csi-boot-vol-pgb1-oqpm7een available 100 3000 general-purpose attached boot us-east-1 Default
r014-a1f6b311-6e4b-4e27-a216-a0b602471268 csi-boot-vol-qgbi-h76dy77d available 100 3000 general-purpose attached boot us-east-1 Default
r014-158e904d-0d48-4090-b6c1-57617c1fcc20 csi-boot-vol-txmz-54wzen5m available 100 3000 general-purpose attached boot us-east-1 Default
r014-dee9736d-08ee-4992-ba8d-3b64a4f0baac demo-volume-update available 100 3000 general-purpose attached data us-east-1 defaults
Command examples 



* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 bx2-2x8 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8
* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 bx2-2x8 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --volume-attach '[{"volume": {"name":"my-volume-name", "capacity":10, "profile": {"name": "general-purpose"},"user_tags": "my-tag-1"]}}]' Create instance with volume attachment.
* ibmcloud is instance-create my-instance-name 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 us-south-1 bx2-2x8 72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --image r123-72b27b5c-f4b0-48bb-b954-5becc7c1dcb8 --volume-attach '[{"volume": {"id":"67531475-bd8a-478e-bcfe-2e53365cd0aa"}}]' Create instance with existing volume in volume attachment.
Check the file systems on both servers. Your output should be similar to the following output.



[root@e2e1270 ] df -h
Filesystem		 Size Used Avail Use% Mounted on
/dev/sda3 879G 1,5G 833G 1% /
tmpfs 16G 0 16G 0% /dev/shm
/dev/sda1 248M 63M 173M 27% /boot
/dev/sdb2 849G 201M 805G 1% /usr/sap
db192-priv:/usr/sap/trans
165G 59M 157G 1% /usr/sap/trans
db192-priv:/sapmnt/C10
165G 59M 157G 1% /sapmnt/C10

[root@sdb192 ] df -h
Filesystem 	 Size Used Avail Use% Mounted on
/dev/sda3 549G 2,3G 519G 1% /
tmpfs 127G 0 127G 0% /dev/shm
/dev/sda1 248M 63M 173M 27% /boot
/dev/mapper/mpath1 493G 70M 468G 1% /backup
/dev/mapper/datavg-datalv
1,2T 71M 1,1T 1% /db2
/dev/mapper/datavg-saplv
165G 60M 157G 1% /usr/sap
/dev/mapper/datavg-sapmntlv
165G 60M 157G 1% /sapmnt

If you install an SAP NetWeaver-based SAP application on IBM Db2, you must create subdirectories under /backup owned by the database admin user (db2SID) for full backups and archived log files. To automatically archive the log files, set LOGMETH1 in your Db2 on Cloud database.
--------- -------- ----- ---- ------------- -------- ------ -------
3m 3m 1 {ibm.io/ibmc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal Provisioning External provisioner is provisioning volume for claim "default/my-persistent-volume-claim"
3m 1m 10 {persistentvolume-controller } Normal ExternalProvisioning can't find provisioner "ibm.io/ibmc-file", expecting that a volume for the claim is provisioned either manually or via external software
1m 1m 1 {ibm.io/ibmc-file 31898035-3011-11e7-a6a4-7a08779efd33 } Normal ProvisioningSucceeded Successfully provisioned volume pvc-0d787071-3a67-11e7-aafc-eef80dd2dea2
4. To mount the storage to your deployment, create a configuration .yaml file and specify the PVC that binds the PV.

If you have an app that requires a non-root user to write to the persistent storage, or an app that requires that the mount path is owned by the root user, see [Adding non-root user access to NFS File Storage for Classic](https://cloud.ibm.com/docs/openshift?topic=openshift-nonroot).

apiVersion: apps/v1
kind: Deployment
metadata:
name: <deployment_name>
labels:
app: <deployment_label>
spec:
selector:
matchLabels:
app: <app_name>
template:
metadata:
labels:
app: <app_name>
spec:
containers:
- image: <image_name>
name: <container_name>
volumeMounts:
- name: <volume_name>
"href": "https://us-south.iaas.cloud.ibm.com/v1/images/de066f7d-b95f-4ca2-9aa0-b6362889e933",
"id": "de066f7d-b95f-4ca2-9aa0-b6362889e933",
"name": "ubuntu-20-04-minimal-amd64-1"
},
"source_volume": {
"crn": "crn:...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/volumes/8948ad59-bc0f-7510-812f-5dc64f59fab8",
"id": "8948ad59-bc0f-7510-812f-5dc64f59fab8",
"name": "instance-vol1"
},
"user_tags": ]
},
{
"bootable": true,
"clones": ],
"created_at": "2022-12-17T20:11:28Z",
"crn": "crn:...]",
"deletable": true,
"encryption": "user_managed",
"encryption_key": {
"crn": "crn:...]"
},
"href": "https://us-south.iaas.cloud.ibm.com/v1/snapshots/e5bfa329-0e36-433f-a3bb-0df632e79263",
"id": "e5bfa329-0e36-433f-a3bb-0df632e79263",
"lifecycle_state": "stable",
"minimum_capacity": 100,