Skip to main content

Remove Unused Logical Volume(lvm) from Linux

1. Un-mount the desired lvm mount point:

[root@hostname ~]# umount /mount_point

i.e.

[root@hostname ~]# umount /u02

Here /u02 is the unwanted mount point that will no longer be needed in my case.

2. Remove the mount point entry from /etc/fstab file:

[root@hostname ~]# vim /etc/fstab

UUID=bbc37d9d-f553-486b-81e9-c2cae03e434a /u02 xfs defaults 0 0

In my case, I need to remove the above line.

3. Remove the associated Logical volume:

3.1. See the list of Logical volume,

[root@hostname ~]# lvdisplay

or

[root@hostname ~]# lvs

3.2. Now, remove the right Logical volume,

[root@hostname ~]# lvremove /dev/vg_name/lv_name

i.e.

[root@hostname ~]# lvremove /dev/vg_u02/lv_u02

4. Now, remove the associated Volume group:

4.1. See the list of Volume group,

[root@hostname ~]# vgdisplay

or

[root@hostname ~]# vgs

4.2 Now, remove the right Volume group,

[root@hostname ~]# vgremove vg_name

i.e.

[root@hostname ~]# vgremove vg_u02

5. Now, remove the associated Physical volume:

5.1. See the list of Physical volume,

[root@hostname ~]# pvdisplay

or

[root@hostname ~]# pvs

5.2 Now, remove the right Physical volume,

You must verify that your Physical volume does not assign to any Volume group before performing this step.

[root@hostname ~]# pvremove /dev/disk_partition_name

i.e.

[root@hostname ~]# pvremove /dev/sdc1

6. Now remove the associated disk if possible or format it again to reuse this disk.

Comments

Popular posts from this blog

Upgrading Issue for RHEL 7 to 8 With Leapp

Overview The Leapp utility is a framework for updating and upgrading operating systems as well as applications. The operations of this utility consist of two phases 1. the preupgrade Phase – that chack the upgrade possibilities and 2. the actual upgrade phase – that map packages between previous and current versions of the software packages. Issue – 01: After running ‘ sudo leapp preupgrade ‘ sometimes you find the below issue in ‘ /var/log/leapp/leapp-report.txt ‘. Detail: Risk Factor: high (inhibitor) Title: Leapp detected loaded kernel drivers which have been removed in RHEL 8. Upgrade cannot proceed. Summary: Support for the following RHEL 7 device drivers has been removed in RHEL 8: – pata_acpi Key: f08a07da902958defa4f5c2699fae9ec2eb67c5b Remediation: 1. Disable detected kernel drivers in order to proceed with the upgrade process using the rmmod or modprobe -r . rmmod – Simple program to remove a module from the Linux Kernel modprobe – Add and remove modules from the Linux Ke...

ORA-00800: soft external error arguments

The problem as stated: After upgrading the Oracle Database from 12c to 19c the following error generated in the alert log file. Actual Oracle Error Code: ORA-00800 After Upgrading from 12c to 19c ORA-00800: soft external error, arguments occured Oracle Database Enterprise 19c fails to start with error: ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM] Why does Insights prevent Oracle grid services from starting How to configure the User slice to allow Real-Time Scheduling for user processes In Alert Log: Errors in file /u01/app/oracle/diag/rdbms/orclproddbone/orclprod/trace/psbcdb_vktm_3529.trc (incident=1200048) (PDBNAME=CDB$ROOT): ORA-00800: soft external error, arguments: [Set Priority Failed], [VKTM], [Check traces and OS configuration], [Check Oracle document and MOS notes], [] Incident details in: /u01/app/oracle/diag/rdbms/orclproddbone/orclprod/incident/incdir_1200048/psbcdb_vktm_3529_i1200048.trc 2023-10-30T10:04:53.536165+06:00 Error attempting to elev...

The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available

The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. 1.0. error message: Error Message: The Oracle Management Server (OMS) host and port specified via OMS_HOST and EM_UPLOAD_PORT is not available. Pass in a valid hostname and port number for the OMS to successfully deploy the agent. 1.1. deploy log: Log: /opt/gc_inst/em/EMGC_OMS1/sysman/agentpush/2023-11-07_16-09-23-PM/applogs/dblivesrv_deploy.log Execution of command cd /opt/agent/ADATMP_2023-11-07_16-09-23-PM;/opt/agent/ADATMP_2023-11-07_16-09-23-PM/agentDeploy.sh -ignorePrereqs ORACLE_HOSTNAME=dblivesrv AGENT_BASE_DIR=/opt/agent OMS_HOST=oemsrv.localdomain EM_UPLOAD_PORT=4903 AGENT_INSTANCE_HOME=/opt/agent/agent_inst b_doDiscovery=false START_AGENT=false b_forceInstCheck=true -force AGENT_PORT=3872 on host dblivesrv Failed 1.2. oms details: [oracle@oemsrv ~]$ $OMS_HOME/bin/emctl status oms -details Oracle Enterprise Manager Cloud Control 13c Release 5 Copyright (c) 1996, 2...