때때로 ext4 오류가 발생하고 디스크가 읽기 전용이 됩니다.
재부팅하면 해결되는데 fcsk /dev/sda2계속 반복되더라구요...
다음은 일부입니다 dmesg:
[ 3160.692730] perf: interrupt took too long (2509 > 2500), lowering kernel.perf_event_max_sample_rate to 79500
[ 3631.408303] perf: interrupt took too long (3144 > 3136), lowering kernel.perf_event_max_sample_rate to 63500
[ 4143.729000] perf: interrupt took too long (3992 > 3930), lowering kernel.perf_event_max_sample_rate to 50000
[ 4770.574303] perf: interrupt took too long (5018 > 4990), lowering kernel.perf_event_max_sample_rate to 39750
[ 5334.077445] perf: interrupt took too long (6289 > 6272), lowering kernel.perf_event_max_sample_rate to 31750
[ 8241.921553] acer_wmi: Unknown function number - 8 - 1
[11370.110956] perf: interrupt took too long (7918 > 7861), lowering kernel.perf_event_max_sample_rate to 25250
[11484.098212] acer_wmi: Unknown function number - 8 - 0
[11875.568601] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.575273] Aborting journal on device sda2-8.
[11875.575537] EXT4-fs error (device sda2) in ext4_da_write_end:3209: IO failure
[11875.575976] EXT4-fs (sda2): Remounting filesystem read-only
[11875.576792] EXT4-fs error (device sda2): ext4_journal_check_start:61: Detected aborted journal
[11875.577612] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.583499] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11875.832886] EXT4-fs error (device sda2): ext4_iget:4862: inode #92441: comm TaskSchedulerFo: bad extra_isize 9489 (inode size 256)
[11899.686408] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686483] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686587] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686656] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686719] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686781] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686844] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.686938] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
[11899.686999] systemd-journald[395]: Failed to write entry (21 items, 614 bytes), ignoring: Read-only file system
[11899.687084] systemd-journald[395]: Failed to write entry (21 items, 705 bytes), ignoring: Read-only file system
그리고 내 /etc/fstab:
UUID=9c882ba5-b980-4f7d-dd02-cd0a1831ab1a / ext4 errors=remount-ro 0 1
UUID=0E37-D0A2 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
이 오류를 제거하거나 변경 remount-ro하고 무시해야 합니까? fstab이 오류를 해결/방지하는 방법은 무엇입니까?
답변1
디스크에 불량 섹터나 블록이 있는지 확인할 수 있습니까? 당신은 그것을 사용할 수 있습니다불량 블록또는지능형 제어Linux를 확인하는 명령을 실행하면 불량 디스크가 문제의 유일한 원인인 것 같습니다.