|
有台作qmail的linux服务器,某次启动后,发现/var区不能写入文件,报空间已经满了,qmail于是罢工。
用df 查看,发现还有50%空闲空间,故用 e2fsck 来查这个分区,查到有错,并进行了修复。
但是过了几秒钟,再次使用e2fsck,发现又有问题,再修复。这样一直循环不断。
也就是说,这个分区上的错误修好了,又不断出现新的错误。我查了一下,没有坏区,请问这是怎么回事啊?
Checking for bad blocks (read-only test): done
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
Block bitmap differences: +16692 +16693
Fix? yes
Free blocks count wrong for group #2 (7221, counted=7219).
Fix? yes
Free blocks count wrong (192458, counted=192456).
Fix? yes
/var: ***** FILE SYSTEM WAS MODIFIED *****
/var: 855/66264 files (8.0% non-contiguous), 72585/265041 blocks
过几秒钟再检查,又出来错误了:
Checking for bad blocks (read-only test): done
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
Block bitmap differences: +16694 +16695 -91094 -91095 -91096 -91097 -91098 -91099
Fix? yes
Free blocks count wrong for group #2 (7219, counted=7217).
Fix? yes
Free blocks count wrong for group #11 (3302, counted=3308).
Fix? yes
Free blocks count wrong (192448, counted=192452).
Fix? yes
/var: ***** FILE SYSTEM WAS MODIFIED *****
/var: 855/66264 files (8.0% non-contiguous), 72589/265041 blocks
这可怎么办啊,一直有错误出来的。
:confused: |
|