![Loop0 上的 EXT4-fs 错误](https://linux22.com/image/13598/Loop0%20%E4%B8%8A%E7%9A%84%20EXT4-fs%20%E9%94%99%E8%AF%AF.png)
我有 Debian 10,安装了最新的 Proxmox。
2 个 SSD,具有:
sda1: EFI
sda2: raid1 (/dev/md0)
sda3: swap
sdb1: EFI (clone of sda1)
sdb2: raid1 (/dev/md0)
sdb3: swap
更新后,我想用 dd 将 /dev/sda1 克隆到 /dev/sdb1,但我犯了一个错误并输入了dd if=/dev/sda of=/dev/sdb
.我用 Ctrl+C 取消了它,执行了正确的命令dd if=/dev/sda1 of=/dev/sdb1
并重新启动。
系统似乎可以工作,但我的日志中有以下错误:
Feb 02 20:50:01 Yggdrasil kernel: EXT4-fs error (device loop0): ext4_lookup:1704: inode #174282: comm php: deleted inode referenced: 174769
Feb 02 20:50:01 Yggdrasil kernel: EXT4-fs error (device loop0): ext4_lookup:1704: inode #174282: comm php: deleted inode referenced: 174769
Feb 02 20:50:01 Yggdrasil kernel: EXT4-fs error (device loop0): ext4_lookup:1704: inode #174282: comm php: deleted inode referenced: 174769
Feb 02 20:50:01 Yggdrasil kernel: EXT4-fs error (device loop0): ext4_lookup:1704: inode #174282: comm php: deleted inode referenced: 174769
Feb 02 20:50:01 Yggdrasil kernel: EXT4-fs error (device loop0): ext4_lookup:1704: inode #174282: comm php: deleted inode referenced: 174769
Feb 02 20:50:01 Yggdrasil kernel: EXT4-fs error (device loop0): ext4_lookup:1704: inode #174282: comm php: deleted inode referenced: 174769
Feb 02 20:50:01 Yggdrasil kernel: EXT4-fs error (device loop0): ext4_lookup:1704: inode #174282: comm php: deleted inode referenced: 174769
Feb 02 20:50:01 Yggdrasil kernel: EXT4-fs error (device loop0): ext4_lookup:1704: inode #174282: comm php: deleted inode referenced: 174769
Feb 02 20:50:01 Yggdrasil kernel: EXT4-fs error (device loop0): ext4_lookup:1704: inode #174282: comm php: deleted inode referenced: 174769
Feb 02 20:50:01 Yggdrasil kernel: EXT4-fs error (device loop0): ext4_lookup:1704: inode #174282: comm php: deleted inode referenced: 174769
我fsck
在救援模式下运行,但似乎没有发现这些错误,因为它们继续在日志中弹出。
谁能帮我?
答案1
解释错误:
该错误并不表示物理磁盘有问题;而是表示物理磁盘有问题。loop0
是一个环回设备。这是一种块存储设备,使用磁盘上的文件作为后备存储。您可能会说是磁盘中的磁盘。这些环回磁盘有自己的文件系统,有时还有自己的分区表。因此,在保存它们的物理磁盘上运行 fsck 不会产生任何效果
解决方案
找到支持循环设备的文件losetup -a | grep loop0
并在其上运行 fsck
答案2
已解决:我找到了罪魁祸首。这是我的 lxc 图片之一。
我跑了e2fsck /var/lib/vz/images/100/vm-100-disk-0.raw
,现在错误消失了。