☰

Journal 已中止 ext4

tag-icon • tag-icon ext4
Journal 已中止 ext4

您好，在 VirtualBox 中的 CentOS 来宾中，我刚刚意识到我的 FS 被安装为只读。

从dmesg我得到：

[ 1725.767566] EXT4-fs error (device sda1) in ext4_ext_remove_space:3028: Journal has aborted
[ 1725.767736] EXT4-fs error (device sda1) in ext4_ext_truncate:4659: Journal has aborted
[ 1725.767889] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4977: Journal has aborted
[ 1725.768037] EXT4-fs error (device sda1) in ext4_truncate:3865: Journal has aborted
[ 1725.768190] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4977: Journal has aborted
[ 1725.768358] EXT4-fs error (device sda1) in ext4_orphan_del:2675: Journal has aborted
[ 1725.768362] EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
[ 1725.768368] EXT4-fs (sda1): Remounting filesystem read-only
[ 1725.768495] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4977: Journal has aborted

不太确定发生了什么。

我将完整的 dmesg 粘贴到http://codepad.org/ucIJZXmC

答案1

内核报告 ATA 磁盘错误：

[ 1719.649797] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
[ 1719.649805] ata1.00: failed command: FLUSH CACHE
[ 1719.649820] ata1.00: cmd e7/00:00:00:00:00/00:00:00:00:00/a0 tag 2
         res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[ 1719.649828] ata1.00: status: { DRDY }
[ 1719.649847] ata1: hard resetting link
[ 1719.956121] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 1719.956802] ata1.00: configured for UDMA/133
[ 1719.956808] ata1.00: retrying FLUSH 0xe7 Emask 0x4
[ 1720.755202] ata1.00: FLUSH failed Emask 0x1
[ 1720.755211] ata1.00: device reported invalid CHS sector 0
[ 1720.755293] ata1: EH complete

经过几次这样的操作后，文件系统驱动程序将中止日志并切换到只读模式。在物理系统上，这些错误通常表示磁盘硬件故障。

[ 1725.742159] Aborting journal on device sda1-8.

[ 1725.768368] EXT4-fs (sda1): Remounting filesystem read-only
[ 1725.768495] EXT4-fs error (device sda1) in ext4_reserve_inode_write:4977: Journal has aborted
[ 1896.091367] ata1: failed to read log page 10h (errno=-5)
[ 1896.091375] ata1.00: NCQ disabled due to excessive errors

但由于这种情况发生在 VirtualBox 来宾虚拟机中，因此可能还有其他原因。例如，可移动媒体上的虚拟机是否被意外拔出？

或者物理上包含虚拟机磁盘映像的磁盘实际上是否出现故障？

或者主机系统上是否有防病毒软件尝试检查虚拟机磁盘映像是否有病毒，从而导致写入操作延迟？

相关内容