RHEL5.8 ext3文件系统损坏的只检测不修复(fsck -n)

最新推荐文章于 2025-03-03 18:11:35 发布

原创最新推荐文章于 2025-03-03 18:11:35 发布 · 4.1k 阅读

0 ·

CC 4.0 BY-SA版权

Linux 专栏收录该内容

292 篇文章

订阅专栏

本文展示了如何使用fsck工具以只读模式检查RHEL5.8系统中ext3文件系统的错误，包括警告信息及检测到的具体问题，并强调了fsck工具修复文件系统操作的风险。

RHEL5.8 ext3文件系统损坏的只检测不修复(fsck -n)

[root@lei1 ~]# df -Th
Filesystem    Type    Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
              ext3    872G  345G  482G  42% /
/dev/sda1     ext3    190M   13M  168M   7% /boot
tmpfs        tmpfs    2.0G     0  2.0G   0% /dev/shm
[root@lei1 ~]# uname -r
2.6.18-308.el5
[root@lei1 ~]# uname -a
Linux lei1 2.6.18-308.el5 #1 SMP Fri Jan 27 17:17:51 EST 2012 x86_64 x86_64 x86_64 GNU/Linux
[root@lei1 ~]# 
[root@lei1 ~]# 
[root@lei1 ~]# fsck -n /dev/mapper/VolGroup00-LogVol00
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
Warning!  /dev/mapper/VolGroup00-LogVol00 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
/dev/mapper/VolGroup00-LogVol00 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 67141633 has zero dtime.  Fix? no

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -76226569
Fix? no

Free blocks count wrong for group #643 (1459, counted=1458).
Fix? no

Free blocks count wrong for group #2326 (31294, counted=31293).
Fix? no

Free blocks count wrong (127388309, counted=137957667).
Fix? no

Inode bitmap differences:  -67141633
Fix? no

Free inodes count wrong (235607546, counted=235607894).
Fix? no


/dev/mapper/VolGroup00-LogVol00: ********** WARNING: Filesystem still has errors **********

/dev/mapper/VolGroup00-LogVol00: 158214/235765760 files (1.1% non-contiguous), 108361067/235749376 blocks
[root@lei1 ~]#

再次强调，fsck -y 修复文件系统，是一件很危险的事情，我曾经遇到过fsck -y 之后，fsck直接把文件给删除了。。。