¿Por qué el nivel de fragmentación es tan grande en los files que contienen otros filesystems?
雖然我不太清楚什麼東西導致它有問題 : # xfs_repair -n /dev/sdb1. /dev/disk/by-id/ata-ST2000DM006-2DM164_Z4Z7ZGB6 /dev/disk/by-path/pci-0000:0a:00.0-ata-1-part1 E: flAbsPath on /var/lib/dpkg/status failed - realpath (117: Structure needs cleaning) E: Could not open file - open (2: No such file or directory) E: Problem opening E: The package lists or status file could not be parsed or opened. I have two 2TB xfs volumes and earlier today the /var/log/messages shows "xfs_force_shutdown" after many errors (attached) var-log-message.txt . mount: Structure needs cleaning. Normally, the fsck program will try to handle filesystems on different physical disk drives in parallel to reduce the total amount of time needed to check all of the filesystems (see: fsck(8)). 我用了下列的指令解決了. ... (17-May-2010) fsck.ext4: Superblock invalid, trying backup blocks... fsck.ext4: Bad magic number in super-block while trying to open /dev/sdf The superblock could not be read or does not describe a correct ext2 filesystem. When you run the fsck on the card from another system, which will be better than going into emergency system, make sure to run mount or "cat … Ask Question Asked 8 years, 10 months ago. ext4 espacio utilizado (opción no-m, files no eliminados) ¿Cómo encuentro el desplazamiento de un sistema de files ext4? I think there is a problem with the file-system. Recovery via fsck. Desventajas de un número creciente de inodos en EXT4; Porcentaje máximo recomendado para llenar una gran unidad de datos ext4 一般情况修复后均可挂载， 但是如果磁盘有问题，或者阵列出问题时此种修复可能会失败，挂载时依然要求格盘，那就果断的格盘吧
上面指令還不能完全解決 ext4文件系统，使用命令 fsck.ext4 /dev/md0 修复， 如果是xfs文件系统，使用命令 xfs_repair -L /dev/md0修复， # mount /dev/sdb1 /disk2 mount: Structure needs cleaning. ext4文件系统，使用命令 fsck.ext4 /dev/xxx 修复， 如果是xfs文件系统，使用命令 xfs_repair -L /dev/xxx修复. fsck stands for "file system check" and it is used to check and optionally repair one or more Linux file systems. I may have been somewhat foolish, but kept putting off the warning signs about the impending failure of my EXT4-on-LVM Ubuntu machine (like the partition remounting itself R/O, SMART errors, etc.) ~ docker info Containers: 0 Running: 0 Paused: 0 Stopped: 0 Images: 0 Server Version: 1.12.0 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Failed to mount '/vendor' (Structure needs cleaning) The filesize of "vendor" looks a bit strange (see picture).