linux-kernel - Re: same ext4 file system corruption on different machines

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 29 Jan 2014 14:05:43 +0100
From:	Luca Ognibene <luca.ognibene@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: same ext4 file system corruption on different machines

Il giorno mer, 29/01/2014 alle 13.52 +0100, Luca Ognibene ha scritto:
> Hi, we are using ext4 as the root file system of some servers(~100, the
> first installed 5 months ago). We are starting to see corruption on
> these file systems, it already happened 3 times. All these servers have
> the same image copied on the 4GB disk-on-module sata disk. They don't
> write very much on the disk, only upgrades from time to time and
> configuration files written 3 times a day,a couple of MB each time. Logs
> are written on another partition. The faulty servers have different
> motherboard/cpu(intel 64bit). We are running ubuntu 12.04.2 with kernel
> 3.8.0-31-generic. We used the same dom with another image and ext3
> without problems for a couple of years so i don't think it's a dom's
> fault.

I've forgot the syslog error entry:

Jan 24 23:00:02 ay kernel: [371845.888834] EXT4-fs error (device sda2):
ext4_iget:3888: inode #127236: comm python-d: bad extra_isize (65663 !=
256)
Jan 24 23:00:02 ay kernel: [371845.888849] Aborting journal on device
sda2-8.
Jan 24 23:00:02 ay kernel: [371845.890819] EXT4-fs (sda2): Remounting
filesystem read-only
Jan 24 23:00:02 ay kernel: [371845.902919] EXT4-fs error (device sda2):
ext4_iget:3888: inode #127236: comm python-d: bad extra_isize (65663 !=
256)

I say "same ext4 file system corruption" because e2fsck reports errors
on inodes around 127233 on all file systems. I'm not sure about the
syslog errors because i have syslog logs for only the latest faulty
partition.

ciao
Luca


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/