From: Theodore Ts'o <tytso@mit.edu>
To: Luca Ognibene <luca.ognibene@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: same ext4 file system corruption on different machines
Date: Thu, 30 Jan 2014 22:00:28 -0500 [thread overview]
Message-ID: <20140131030028.GB7118@thunk.org> (raw)
In-Reply-To: <1391068749.2680.6.camel@snow.station>
On Thu, Jan 30, 2014 at 08:59:09AM +0100, Luca Ognibene wrote:
> Yes it's indeed very strange.. i tend to rule out application errors
> because i don't write directly to the device so i don't think i can
> break a filesystem from userspace. I've checked previous and next blocks
> and they seem ok, only the block 524320 is getting corrupted. Any idea
> on what should i look for now?
Are you willing to try 3.12.9 or 3.13.1 upstream kernel? Let's see if
changing the kernel makes any difference. I don't recall any ext4
problems like this, but maybe it's device driver problem.
The other thing I'd ask is whether you can swap out the hard drive
interface --- can you use a USB 3.0 attached drive, or something like
that?
One final thing that you could try doing, depending on how
easily/quickly you can reproduce the problem, is to use blktrace and
see if you can catch who or what is writing to that specific block
which is getting corrupted.
- Ted
next prev parent reply other threads:[~2014-01-31 3:00 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
2014-01-29 17:38 ` Theodore Ts'o
2014-01-30 7:59 ` Luca Ognibene
2014-01-31 3:00 ` Theodore Ts'o [this message]
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=20140131030028.GB7118@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.ognibene@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.