From: Luca Ognibene <luca.ognibene@gmail.com>
To: "Theodore Ts'o" <tytso@mit.edu>
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 12:02:47 +0100 [thread overview]
Message-ID: <1391079767.2680.18.camel@snow.station> (raw)
In-Reply-To: <20140129173826.GA30419@thunk.org>
Il giorno mer, 29/01/2014 alle 12.38 -0500, Theodore Ts'o ha scritto:
> On Wed, Jan 29, 2014 at 02:05:43PM +0100, Luca Ognibene wrote:
> > I say "same ext4 file system corruption" because e2fsck reports errors
> > on inodes around 127233 on all file systems.a I'm not sure about the
> > syslog errors because i have syslog logs for only the latest faulty
> > partition.
>
Sorry i made a mistake in the first email. These dom drives are IDE, not
SATA.
ciao
Luca
prev parent reply other threads:[~2014-01-30 11:02 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
2014-02-04 9:05 ` Luca Ognibene
2014-01-30 11:02 ` Luca Ognibene [this message]
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=1391079767.2680.18.camel@snow.station \
--to=luca.ognibene@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tytso@mit.edu \
/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