From: Luca Ognibene <luca.ognibene@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: same ext4 file system corruption on different machines
Date: Wed, 29 Jan 2014 14:05:43 +0100 [thread overview]
Message-ID: <1391000743.2601.26.camel@snow.station> (raw)
In-Reply-To: <1390999955.2601.22.camel@snow.station>
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
next prev parent reply other threads:[~2014-01-29 13:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-29 12:52 same ext4 file system corruption on different machines Luca Ognibene
2014-01-29 13:05 ` Luca Ognibene [this message]
2014-01-29 17:38 ` Theodore Ts'o
2014-01-30 7:59 ` Luca Ognibene
2014-01-31 3:00 ` Theodore Ts'o
2014-02-04 9:05 ` Luca Ognibene
2014-01-30 11:02 ` Luca Ognibene
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1391000743.2601.26.camel@snow.station \
--to=luca.ognibene@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox