linux – ext4文件系统损坏 – 可能是硬件错误？

概述我打开电脑约半小时后,我在dmesg中收到这些错误： [ 1355.677957] EXT4-fs error (device sda2): htree_dirblock_to_tree: inode #1318420: (comm updatedb.mlocat) bad entry in directory: directory entry across blocks - block=5251 我打开电脑约半小时后,我在dmesg中收到这些错误：

[ 1355.677957] EXT4-fs error (device sda2): htree_dirblock_to_tree: inode #1318420: (comm updatedb.mlocat) bad entry in directory: directory entry across blocks - block=5251700offset=0(0),inode=1802725748,rec_len=179136,name_len=32 [ 1355.677973] Aborting journal on device sda2-8. [ 1355.678101] EXT4-fs (sda2): Remounting filesystem read-only [ 1355.690144] EXT4-fs error (device sda2): htree_dirblock_to_tree: inode #1318416: (comm updatedb.mlocat) bad entry in directory: directory entry across blocks - block=5251699offset=0(0),inode=2194783952,rec_len=53280,name_len=152 [ 1356.864720] EXT4-fs error (device sda2): htree_dirblock_to_tree: inode #1312795: (comm updatedb.mlocat) bad entry in directory: directory entry across blocks - block=5251176offset=1460(13748),inode=1432317541,rec_len=208208,name_len=119

/ dev / sda是​​一个SSD,它使用noop调度程序.

/ etc / fstab条目：

UUID=acb4eefa-48ff-4ee1-bb5f-2dccce7d011f / ext4 errors=remount-ro,noatime,discard,user_xattr 0 1

系统信息：

$cat /proc/mounts | grep /dev/sd/dev/sda1 /boot ext2 rw,errors=continue 0 0$cat /etc/lsb-release disTRIB_ID=UbuntudisTRIB_RELEASE=10.04disTRIB_CODEname=lucIDdisTRIB_DESCRIPTION="Ubuntu 10.04.3 LTS"$uname -alinux leetpad 2.6.35-30-generic-pae #61~lucID1-Ubuntu SMP Thu Oct 13 21:14:29 UTC 2011 i686 GNU/linux

智能输出-a：

smartctl version 5.38 [i686-pc-linux-gnu] copyright (C) 2002-8 Bruce AllenHome page is http://smartmontools.sourceforge.net/=== START OF informatION SECTION ===Device Model:     STT_FTM28GX25HSerial Number:    P637510-MIBY-706A009Firmware Version: 1916User Capacity:    128,035,676,160 bytesDevice is:        Not in smartctl database [for details use: -P showall]ATA Version is:   8ATA Standard is:  Exact ATA specification draft version not indicatedLocal Time is:    Thu Nov 24 20:53:48 2011 UTCSMART support is: Available - device has SMART capability.SMART support is: Enabled=== START OF READ SMART DATA SECTION ===SMART overall-health self-assessment test result: PASSEDSee vendor-specific Attribute List for marginal Attributes.General SMART Values:Offline data collection status:  (0x00) Offline data collection activity                    was never started.                    auto Offline Data Collection: Disabled.Self-test execution status:      (   0) The prevIoUs self-test routine completed                    without error or no self-test has ever                     been run.Total time to complete Offline data collection:         (   0) seconds.Offline data collectioncapabilitIEs:            (0x1d) SMART execute Offline immediate.                    No auto Offline data collection support.                    Abort Offline collection upon new                    command.                    Offline surface scan supported.                    Self-test supported.                    No Conveyance Self-test supported.                    No Selective Self-test supported.SMART capabilitIEs:            (0x0003) Saves SMART data before entering                    power-saving mode.                    Supports SMART auto save timer.Error logging capability:        (0x00) Error logging NOT supported.                    General Purpose Logging supported.Short self-test routine recommended polling time:    (   0) minutes.Extended self-test routinerecommended polling time:    (   0) minutes.SMART Attributes Data Structure revision number: 16vendor Specific SMART Attributes with Thresholds:ID# ATTRIBUTE_name          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_Failed RAW_VALUE  1 Raw_Read_Error_Rate     0x0000   005   000   000    old_age   Offline  In_the_past 0  9 Power_On_Hours          0x0000   141   002   000    old_age   Offline      -       0 12 Power_Cycle_Count       0x0000   115   002   000    old_age   Offline      -       0184 UnkNown_Attribute       0x0000   084   000   000    old_age   Offline  In_the_past 0195 HarDWare_ECC_Recovered  0x0000   000   000   000    old_age   Offline  FAIliNG_Now 0196 Reallocated_Event_Count 0x0000   000   000   000    old_age   Offline  FAIliNG_Now 0197 Current_Pending_Sector  0x0000   000   000   000    old_age   Offline  FAIliNG_Now 0198 Offline_Uncorrectable   0x0000   002   107   000    old_age   Offline      -       21198199 UDMA_CRC_Error_Count    0x0000   063   003   000    old_age   Offline      -       26957200 Multi_Zone_Error_Rate   0x0000   099   124   000    old_age   Offline      -       446201 Soft_Read_Error_Rate    0x0000   024   154   000    old_age   Offline      -       328202 TA_Increase_Count       0x0000   115   254   000    old_age   Offline      -       115203 Run_Out_Cancel          0x0000   247   245   000    old_age   Offline      -       83204 Shock_Count_Write_Opern 0x0000   000   000   000    old_age   Offline  FAIliNG_Now 0205 Shock_Rate_Write_Opern  0x0000   016   039   000    old_age   Offline      -       0206 Flying_Height           0x0000   005   000   000    old_age   Offline  In_the_past 0207 Spin_High_Current       0x0000   055   015   000    old_age   Offline      -       0208 Spin_Buzz               0x0000   248   001   000    old_age   Offline      -       0209 Offline_Seek_Performnce 0x0000   095   000   000    old_age   Offline  In_the_past 0211 UnkNown_Attribute       0x0000   000   000   000    old_age   Offline  FAIliNG_Now 0212 UnkNown_Attribute       0x0000   000   000   000    old_age   Offline  FAIliNG_Now 0213 UnkNown_Attribute       0x0000   000   000   000    old_age   Offline  FAIliNG_Now 0Warning: device does not support Error LoggingWarning! SMART ATA Error Log Structure error: invalID SMART checksum.SMART Error Log Version: 1No Errors LoggedWarning! SMART Self-Test Log Structure error: invalID SMART checksum.SMART Self-test log structure revision number 1No self-tests have been logged.  [To run self-tests,use: smartctl -t]Device does not support Selective Self Tests/Logging

我运行memtest 7个小时,它没有发现任何内存错误.

任何明显的想法在这种情况下会出现什么问题？我能想象到的最合理的事情是SSD正在静默地丢弃一些写请求,最终导致EXT4文件系统不一致(但没有磁盘I / O错误).怎么会发生这种情况？是否有相关的配置选项我应该确保正确设置？

我应该使用哪些工具来诊断硬件故障？是否可以在不覆盖数据的情况下诊断SSD故障？

解决方法 首先,您可能希望对根磁盘执行完整的fsck.有时,我发现快速检查有时会遗漏一些重要的错误.您可以通过触摸根目录中的文件(可能取决于linux发行版)来执行此 *** 作,但可以尝试

touch /forcefsck

并重新启动或启动救援CD并在那里执行root的fsck.完整,我的意思是使用-f fsck参数.

第二,您的系统日志是否指示任何硬件错误？

正如Kario先生所说,您可能会考虑使用smartctl检查磁盘运行状况.我发现我使用的某些磁盘不会报告信息.

总结

以上是内存溢出为你收集整理的linux – ext4文件系统损坏 – 可能是硬件错误？全部内容，希望文章能够帮你解决linux – ext4文件系统损坏 – 可能是硬件错误？所遇到的程序开发问题。

如果觉得内存溢出网站内容还不错，欢迎将内存溢出网站推荐给程序员好友。