From: Theodore Ts'o <tytso@mit.edu>
To: Angelo Dureghello <angelo70@gmail.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: ext4 errors on kernel 3.17.0
Date: Wed, 19 Nov 2014 08:50:59 -0500 [thread overview]
Message-ID: <20141119135059.GA7131@thunk.org> (raw)
In-Reply-To: <546C968C.60908@gmail.com>
The I/O errors, the "automount: inserted" message, the fact that it
shows up on ext3 and ext4, makes it smell very much like a hardware
problem (or possibly a mmc device driver problem). It could be caused
by a fake mmc card that (if you bought it from a street vendor or some
the micro center discount bin at the checkout counter, try getting a
brand name flash from a reputable source --- you get what you pay
for).
It could be caused by flaky hardware, or a MMC drive; it could be
caused by an MMC driver problem. It doesn't seem like it's a file
system problem.
Regards,
- Ted
next prev parent reply other threads:[~2014-11-19 13:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 16:52 ext4 errors on kernel 3.17.0 Angelo Dureghello
2014-11-19 13:09 ` Angelo Dureghello
2014-11-19 13:50 ` Theodore Ts'o [this message]
2014-11-20 11:16 ` Angelo Dureghello
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=20141119135059.GA7131@thunk.org \
--to=tytso@mit.edu \
--cc=angelo70@gmail.com \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).