[ 228.164144] EXT4-fs error (device sda1): __ext4_ext_check_block:494: inode #60818439: comm postgres: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 228.391834] EXT4-fs error (device sda1): __ext4_ext_check_block:494: inode #60818439: comm postgres: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 228.580610] EXT4-fs error (device sda1) in ext4_ext_truncate:4442: IO failure
could not write to log file: Input/output error
[ 228.668012] EXT4-fs error (device sda1): __ext4_ext_check_block:494: inode #60818439: comm postgres: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 228.696709] EXT4-fs error (device sda1): __ext4_ext_check_block:494: inode #60818439: comm postgres: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 228.716812] EXT4-fs error (device sda1) in ext4_ext_truncate:4442: IO failure
[ 228.772998] EXT4-fs error (device sda1): __ext4_ext_check_block:494: inode #60818439: comm postgres: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 229.374046] EXT4-fs error (device sda1): __ext4_ext_check_block:494: inode #60818439: comm postgres: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 229.562764] EXT4-fs error (device sda1) in ext4_ext_truncate:4442: IO failure
[ 229.655808] EXT4-fs error (device sda1): __ext4_ext_check_block:494: inode #60818439: comm postgres: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 229.847615] EXT4-fs error (device sda1): __ext4_ext_check_block:494: inode #60818439: comm postgres: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 230.036344] EXT4-fs error (device sda1) in ext4_ext_truncate:4442: IO failure
[ 230.318913] EXT4-fs error (device sda1): __ext4_ext_check_block:494: inode #60818439: comm postgres: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 231.180031] EXT4-fs error (device sda1): __ext4_ext_check_block:494: inode #60818439: comm postgres: bad header/extent: invalid magic - magic 0, entries 0, max 0(0), depth 0(0)
[ 231.368739] EXT4-fs error (device sda1) in ext4_ext_truncate:4442: IO failure
nf_conntrack (size 504 buckets 131072 max 2000000) memory:2GB
暂无评论
核心:sda1 盘 EXT4 文件系统损坏、IO 读写失败,postgres 数据库进程触发报错
EXT4-fs error (device sda1): ... bad header/extent: invalid magic
could not write to log file: Input/output error
sda1:设备内置硬盘 / SSD 第一个分区,ACG 的日志、审计、PostgreSQL 审计库都存在这个分区;bad header/extent invalid magic:ext4 扩展块元数据损坏,文件索引头标记异常;comm postgres:是 ACG 内置的审计数据库进程,它在写审计日志 / 库文件时读写失败;Input/output error = IO 错误:磁盘介质坏块、文件系统损坏、磁盘硬件故障;最后一行
nf_conntrack是连接跟踪内存打印,不属于故障告警,是正常信息输出,可以忽略。
⚠️ 注意:ACG 内置 postgres 审计库,fsck 不能随便在线跑,容易把数据库搞崩。
#查看磁盘健康(AK230是SSD)
smartctl -a /dev/sda
#看SMART里:Reallocated_Sector、Media_Error、Uncorrectable_Error,有计数=硬件盘坏
dmesg | grep EXT4
只要持续反复刷同一条 ext4 error,大概率两种情况。
操作步骤:
fsck.ext4;H3C ACG 不支持业务在线 fsck,在线修复极易损坏 postgres 数据库,审计直接报废。
could not write to log file👉 文件系统修复无效,修复完重启很快复现相同报错
ACG1000-AK230,dmesg 持续 EXT4-fs sda1 extent invalid magic,postgres 写日志 IO error,已收集 smartctl 信息,需要确认 SSD 是否故障,申请维保。
暂无评论
亲~登录后才可以操作哦!
确定你的邮箱还未认证,请认证邮箱或绑定手机后进行当前操作
举报
×
侵犯我的权益
×
侵犯了我企业的权益
×
抄袭了我的内容
×
原文链接或出处
诽谤我
×
对根叔社区有害的内容
×
不规范转载
×
举报说明
暂无评论