Resolving 'Bad magic number in super-block' Error with resize2fs in CentOS 7

Problem Background and Error Analysis

Disk space expansion is a common administrative task in Linux system management. When using LVM (Logical Volume Manager) for logical volume extension, many administrators encounter the resize2fs: Bad magic number in super-block while trying to open /dev/mapper/centos-root error. This error indicates that the system cannot recognize the filesystem superblock of the target device.

From a technical perspective, the 'magic number' is an identifier in the filesystem superblock used to recognize the filesystem type. When the resize2fs command cannot find a valid superblock, it typically indicates one of two situations: either the filesystem is corrupted, or the current resizing tool does not match the filesystem type.

CentOS 7 Filesystem Characteristics

CentOS 7 defaults to using XFS as the root filesystem, which differs from earlier versions that used ext4. XFS is a high-performance 64-bit journaling filesystem with excellent scalability and reliability. However, this change has caused confusion for many administrators when using traditional tools.

Key differences include:

• resize2fs is specifically designed for resizing ext2/ext3/ext4 filesystems
• xfs_growfs is the dedicated resizing tool for XFS filesystems
• The filesystem recognition mechanisms of the two tools are completely different

Problem Diagnosis Process

To accurately diagnose filesystem type, use the following commands:

# Check filesystem type
df -T /dev/mapper/centos-root
# Or use more detailed filesystem information
lsblk -f /dev/mapper/centos-root
# Direct filesystem information query
file -s /dev/mapper/centos-root

In the provided case, although the user successfully performed LVM extension operations:

# Create new partition
fdisk /dev/xvda
# Extend volume group
pvcreate /dev/xvda3
vgextend centos /dev/xvda3
# Extend logical volume
lvextend -l+288 /dev/centos/root

The incorrect filesystem resizing tool was used in the final step, resulting in the 'Bad magic number' error.

Correct Solution

For XFS filesystems, the correct resizing command is:

# Online resize of XFS filesystem
xfs_growfs /dev/centos/root
# Verify resize results
df -h /dev/mapper/centos-root

How the xfs_growfs command works:

• Reads XFS filesystem superblock information
• Checks filesystem journal integrity
• Extends filesystem to use all available space
• Maintains filesystem online without unmounting

Complete Operation Example

Below is the complete process for correctly extending the root filesystem in CentOS 7:

# Step 1: Create new partition
fdisk /dev/xvda
# In fdisk interactive interface:
# n (new partition)
# p (primary partition)
# 3 (partition number)
# Use default start sector
# Use default end sector
# t (change partition type)
# 8e (Linux LVM)
# w (write and exit)

# Step 2: Reread partition table
partprobe /dev/xvda

# Step 3: Create physical volume and extend volume group
pvcreate /dev/xvda3
vgextend centos /dev/xvda3

# Step 4: Check available space and extend logical volume
vgdisplay -v centos
lvextend -l+100%FREE /dev/centos/root

# Step 5: Resize XFS filesystem
xfs_growfs /dev/centos/root

# Step 6: Verify results
df -h /dev/mapper/centos-root

Technical Deep Dive

Understanding filesystem superblock structure is crucial for diagnosing such issues. The superblock contains critical filesystem metadata:

• Magic Number: Unique identifier for filesystem type
• Block Size: Size of filesystem blocks
• Inode Table: File index node information
• Journal Information: Transaction log for journaling filesystems

The XFS superblock contains the specific magic number 0x58465342 (ASCII representation of 'XFSB'), while ext4's magic number is 0xEF53. When resize2fs searches for ext4's magic number on an XFS filesystem, it naturally cannot find a valid superblock.

Preventive Measures and Best Practices

To avoid such issues, recommend:

1. Confirm filesystem type before operation: df -T or lsblk -f
2. Understand default filesystems of different Linux distributions
3. Verify extension procedures in test environments
4. Backup important data before disk operations
5. Use LVM snapshot functionality to create pre-operation system state backups

Related Tools Comparison

Comparison of resizing tools for different filesystems:

It's important to note that XFS does not support online shrinking, which is a significant difference from ext4.

Conclusion

The 'Bad magic number in super-block' error typically stems from a mismatch between filesystem type and resizing tool. In CentOS 7 and later versions, since XFS is the default filesystem, administrators should use xfs_growfs instead of resize2fs to resize the root filesystem. Proper diagnosis procedures and tool selection are key to successful disk space management.