1. 故障现象

mount: wrong fs type, bad option, bad superblock on /dev/vdb1,       missing codepage or helper program, or other error       In some cases useful info is found in syslog - try       dmesg | tail or so.

2. 故障排除

造成这个故障是因为原来内网的服务器上阿里云.在内网时是用的vg,用SMC上云之后VG就不再支持,默认被转成了vdb1,格式还是xfs
使用命令查看详细报错

dmesg | tail

获取到以下报错

[ 2084.391811] XFS (vdb1): Mounting V5 Filesystem[ 2084.404936] XFS (vdb1): Corruption warning: Metadata has LSN (2077:25717) ahead of current LSN (1:2). Please unmount and run xfs_repair (>= v4.3) to resolve.[ 2084.406745] XFS (vdb1): log mount/recovery failed: error -22[ 2084.407574] XFS (vdb1): log mount failed

那么就尝试修复.

 xfs_repair /dev/vdb1

经过几秒的修复过程

# xfs_repair /dev/vdb1Phase 1 - find and verify superblock...Phase 2 - using internal log        - zero log...        - scan filesystem freespace and inode maps...        - found root inode chunkPhase 3 - for each AG...        - scan and clear agi unlinked lists...        - process known inodes and perfORM inode discovery...        - agno = 0        - agno = 1        - agno = 2        - agno = 3        - agno = 4        - agno = 5        - agno = 6        - agno = 7        - agno = 8        - agno = 9        - agno = 10        - agno = 11        - agno = 12        - process newly discovered inodes...Phase 4 - check for duplicate blocks...        - setting up duplicate extent list...        - check for inodes claiming duplicate blocks...        - agno = 0        - agno = 4        - agno = 8        - agno = 3        - agno = 6        - agno = 5        - agno = 1        - agno = 7        - agno = 9        - agno = 10        - agno = 2        - agno = 11        - agno = 12Phase 5 - rebuild AG headers and trees...        - reset superblock...Phase 6 - check inode connectivity...        - resetting contents of realtime bitmap and summary inodes        - traversing filesystem ...        - traversal finished ...        - moving disconnected inodes to lost+found ...Phase 7 - verify and correct link counts...Maximum metadata LSN (2077:25717) is ahead of log (1:2).Format log to cycle 2080.done

明显这里修复已经完成.
重新mount后故障排除.再把/etc/fstab里的配置修改回来.重启再次检查,故障已经被排除

来源地址：https://blog.csdn.net/qq_29974229/article/details/128198118