主页 / unix / 问题 / 784473
Accepted
gcb
Asked: 2024-10-04 06:28:49 +0800 CST

我是否应该关心 ext4 空闲块/inode/孤立块计数是否错误？

  • 772

我让系统在每次重启时都对所有文件系统进行 fsck。现在又强制进行了 fsck。但我仍然得到：

$ sudo fsck -vn /dev/lvmroot/root 
fsck from util-linux 2.40.2
e2fsck 1.47.1 (20-May-2024)
Warning!  /dev/mapper/lvm/root is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
root has been mounted 1 times without being checked, check forced.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (12783960, counted=12783944).
Fix? no

Free inodes count wrong (5263640, counted=5263625).
Fix? no

Feature orphan_present is set but orphan file is clean.
Clear? no
      503528 inodes used (8.73%, out of 5767168)
         271 non-contiguous files (0.1%)
         237 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
             Extent depth histogram: 448994/96
    10284712 blocks used (44.58%, out of 23068672)
           0 bad blocks
           5 large files

      409720 regular files
       37767 directories
           0 character device files
           0 block device files
           0 fifos
        4248 links
       56022 symbolic links (54421 fast symbolic links)
          24 sockets
------------
      507781 files

我是否应该特意去修复它？

ext4

1 个回答

  1. Best Answer

    在正常的文件系统操作期间，超级块中的空闲块和 inode 计数不会保持更新。这是为了避免当多个线程同时修改文件系统时出现单点争用。

    无需在运行时更新超级块，在挂载时从组描述符中读取空闲块和 inode 并将其保存在内存中。由于文件系统中有数千或数百万个组描述符，因此在运行时锁定这些单个结构的争用率很低。

    • 2

相关问题