Skip to main content

How to reduce LVM partition size in RHEL and OEL

How to reduce LVM partition size in RHEL and OEL


If observe a particular file system is not used fully and a lot of free space is available then we can make some free space in the volume group by reducing the LVM using lvreduce command.

Example:  To reduce /oracle mount by 2GB which is on LVM partition & formated as ext4

[root@funebs122 ~]# df -h /oracle/
 Filesystem            Size  Used Avail Use% Mounted on
 /dev/mapper/vg_funebs122-lvol1
                       12G   9.2G  1.9G  84%  /oracle
   

Steps:
   
   
1. Umount the file system

[root@funebs122 ~]# umount -v /oracle/


2. Check the file system for Errors using e2fsck command

[root@funebs122 ~]# e2fsck -f /dev/mapper/vg_funebs122-lvol1
 e2fsck 1.41.12 (17-May-2010)
 Pass 1: Checking inodes, blocks, and sizes
 Pass 2: Checking directory structure
 Pass 3: Checking directory connectivity
 Pass 4: Checking reference counts
 Pass 5: Checking group summary information
 /dev/mapper/vg_funebs122-lvol1: 12/70640 files (0.0% non-contiguous), 446686/308428 blocks
Note: In the above command e2fsck , we use the option ‘-f’ to forcefully check the file system, even if the file system is clean.


3. Reduce or Shrink the size of /oracle to the desire size.

In my case size of /oracle is 12 GB , so by reducing it by 2GB , then the size will become 10GB.

[root@funebs122 ~]# resize2fs /dev/mapper/vg_funebs122-lvol1 10G
 resize2fs 1.41.12 (17-May-2010)
 Resizing the filesystem on /dev/mapper/vg_funebs122-lvol1 to 2621440 (4k) blocks.
 The filesystem on /dev/mapper/vg_funebs122-lvol1 is now 2621440 blocks long.
 
4. Reduce the size using lvreduce command

[root@funebs122 ~]# lvreduce -L 10G /dev/mapper/vg_funebs122-lvol1
 WARNING: Reducing active logical volume to 10.00 GiB
 THIS MAY DESTROY YOUR DATA (filesystem etc.)
 Do you really want to reduce lvol1? [y/n]: y
 Reducing logical volume lvol1 to 10.00 GiB
 Logical volume lvol1 successfully resized

5. Now check the reduced file system for errors (Optional)

[root@funebs122 ~]# e2fsck -f /dev/mapper/vg_funebs122-lvol1
 e2fsck 1.41.12 (17-May-2010)
 Pass 1: Checking inodes, blocks, and sizes
 Pass 2: Checking directory structure
 Pass 3: Checking directory connectivity
 Pass 4: Checking reference counts
 Pass 5: Checking group summary information
 /dev/mapper/vg_funebs122-lvol1: 12/70640 files (0.0% non-contiguous), 446686/308428 blocks
 
6. Mount the file system and verify its size.

[root@funebs122 ~]# mount /oracle/
 [root@funebs122 ~]# df -h /oracle/
 Filesystem            Size  Used Avail Use% Mounted on
 /dev/mapper/vg_funebs122-lvol1
                       9.9G  9.2G  208M  98% /oracle



Note for XFS file system: 

While the XFS file systems can be grown while mounted, their size cannot be reduced. 

Workarounds may be done:
Use some backup/restore solution, such as xfsdump and xfsrestore. This may be useful especially if the filesystem is mostly empty.

Use the xfs_quota command to implement project (directory tree) quotas. Project quotas implement space limitations for all files within a directory subtree, similar to behavior under a new filesystem mount point.





If you like please follow and comment

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...