Skip to main content

Adding a DISK on GOOGLE Cloud VM

Adding a DISK on GOOGLE Cloud VM


In this post we are going to see how to attach a DISK on Google Cloud VM.

Steps:


1) Attaching a New Disk to VM

Go to your Google Cloud Console and navigate to Compute >> VM Instances.

Click the name of the instance where you want to add a disk.

Click Edit, at the top of the instance details page.

Scroll down to Additional disks and click Add item.

Configure the disk’s properties and click Create.

Scroll down to the bottom of the page and click Save to apply your changes to the instance and attach the new disk.




2) Check the new disk on VM. sbd is the new disk.

[himanshu@ebs122 ~]$ sudo lsblk
NAME   MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda      8:0    0   10G  0 disk 
└─sda1   8:1    0   10G  0 part /
sdb      8:16   0  400G  0 disk

3) Format the Disk

sudo mkfs.ext4 -m 0 -E lazy_itable_init=0,lazy_journal_init=0,discard /dev/[DEVICE_ID]

Note: RHEL 6 and CentOS 6 do not accept the lazy_journal_init=0 argument. Remove this parameter when formatting zonal persistent disks on instances with these images.

sudo mkfs.ext4 -m 0 -F -E lazy_itable_init=0,discard /dev/sdb

4) Mounting the DISK. Create a directory and mount the disk on that.

[himanshu@ebs122 ~]$ sudo mkdir /u01
[himanshu@ebs122 ~]$ sudo mount -o discard,defaults /dev/sdb /u01

5) Change read write permission

sudo chmod a+w /u01

6) Edit the fstab to make sure the mount is permanent after server reboot.

sudo blkid /dev/sdb


echo UUID=`sudo blkid -s UUID -o value /dev/sdb` /u01 ext4 discard,defaults,nofail 0 2 | sudo tee -a /etc/fstab

7) Verify Mount Point

[himanshu@ebs122 ~]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1       9.8G  3.5G  5.8G  38% /
tmpfs           7.3G     0  7.3G   0% /dev/shm
/dev/sdb        394G   71M  394G   1% /u01


Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...