My Oracle Support Banner

OCFS2 mounted.ocfs2 returns 'Unknown: Bad magic number in inode' (Doc ID 431556.1)

Last updated on APRIL 29, 2020

Applies to:

Linux OS - Version Oracle Linux 4.4 and later
Oracle Cloud Infrastructure - Version N/A and later
Linux x86-64
Linux x86
Linux ItaniumLinux x86-64
Oracle Cluster File System Version 2 (OCFS2) 1.x


Symptoms

When running OCFS2 mounted.ocfs2(8) command to check which cluster nodes have OCFS2 volumes mounted, message 'Unknown: Bad magic number in inode' is returned for one one or more devices. Repartitioning (fdisk(8)) or reformatting (mkfs.ocfs2(8)) the device(s) fail to suppress the message.

Changes

The device(s) for which the message is observed, was originally an unpartitioned disk, upon which an OCFS2 filesystem had once been created. The device(s) were subsequently partitioned (whether with or without an OCFS2 filesystem having been created on one or more of the it's partitions).

In the example above, an OCFS2 filesystem was originally created on unpartitioned device /dev/sdc - it was later partitioned and an OCFS2 filesystem created on partition one, /dev/sdc1.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
 1. Backup the device
 2. Locate the redundant OCFS2 superblock
 3. Open the device using a binary editor
 4. Edit the superblock using a binary editor
 5. Verify the 'Unknown: Bad magic number in inode' message does not occur

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