FSCK On Unmounted LVM Volume Returns That Volume "is in use" And "Cannot continue, aborting." (Doc ID 2741031.1)

Last updated on OCTOBER 07, 2022

Applies to:

Goal

In a scenario where an LVM Volume is increased to add more disk space and when resizing the Filesystem(eg. ext4) it shows a similar error:

resize2fs 1.43-WIP (20-Jun-2013)
resize2fs: Permission denied to resize filesystem
Filesystem at <LVM_VOL_DEVICE> is mounted on <DIR_MOUNTPOINT>; on-line resizing required

But the filesystem is umounted and confirmed with the "mount" command and other methods like inspection of the "/proc/mounts" file. When attempting a filesystem check, fsck, similar messages keep showing like it was still in use although umounted.

# fsck -y <LVM_VOL_DEVICE>
e2fsck 1.43-WIP (20-Jun-2013)
<LVM_VOL_DEVICE> is in use.
e2fsck: Cannot continue, aborting.

The "fuser" and "lsof" command over the LVM volume device show nothing using it, leaving the idea that if nothing in the OS is using it it could be a filesystem corruption.

The goal of this document is to offer a Systems Administrator(SysAdmin) an approach to sort or narrow down the source of this issue, Is the kernel/system blocking it, or is the filesystem corrupted.

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.