From: "Theodore Ts'o" <tytso@mit.edu>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>
Subject: Re: ext4: total breakdown on USB hdd, 3.0 kernel
Date: Mon, 30 Jun 2014 09:43:13 -0400 [thread overview]
Message-ID: <20140630134313.GA3753@thunk.org> (raw)
In-Reply-To: <20140630064644.GA23079@amd.pavel.ucw.cz>
On Mon, Jun 30, 2014 at 08:46:44AM +0200, Pavel Machek wrote:
> :-). Aha, and I misremembered, it was block descriptor checksums, not
> inode checksums:
>
> One or more block group descriptor checksums are invalid. Fix? yes
>
> Group descriptor 0 checksum is invalid. FIXED.
> Group descriptor 1 checksum is invalid. FIXED.
> Group descriptor 2 checksum is invalid. FIXED.
> Group descriptor 3 checksum is invalid. FIXED.
Yeah, what we should be doing here is to try to backup block
descriptors and check to see if they are valid, and if so, use them
instead.
> I'm still trying to figure out what went wrong in the OLPC-1.75 + USB
> disk case.
>
> One possibility is that OLPC is unable to provide enough power from
> the two USB ports to power Seagate Momentus 5400.6, and that the hard
> drive fails to detect the brown-out and does something wrong. (Are
> SATA drives expected to work at 4.5V? Because that's what is
> guaranteed on USB, IIRC).
The USB spec seems to require 5V +/i 0.25V, which also seems to be the
spec on laptop drives. It wouldn't surprise me if the OLPC (or its
power adapter) is a bit dodgy under heavy load, though. It might be
useful for you to measure the voltage and amps delivered at the USB
ports
> Heavy corruption happened when I was charging the phone _and_ running
> the hard drive, from the OLPC. Now I have seen cases when OLPC crashed
> on device plug-in, in what looked like a brown-out...
.... and from the power brick to see if either is out of spec.
- Ted
next prev parent reply other threads:[~2014-06-30 13:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 20:20 ext4: total breakdown on USB hdd, 3.0 kernel Pavel Machek
2014-06-26 20:30 ` Pavel Machek
2014-06-26 20:50 ` Pavel Machek
2014-06-27 2:48 ` Theodore Ts'o
2014-06-27 2:46 ` Theodore Ts'o
2014-06-29 20:25 ` Pavel Machek
2014-06-29 21:04 ` Theodore Ts'o
2014-06-30 6:46 ` Pavel Machek
2014-06-30 13:43 ` Theodore Ts'o [this message]
2014-07-04 10:23 ` ext4: media error but where? Pavel Machek
2014-07-04 12:11 ` Theodore Ts'o
2014-07-04 17:21 ` Pavel Machek
2014-07-04 18:06 ` Pavel Machek
2014-07-04 18:56 ` Theodore Ts'o
2014-07-06 13:32 ` Pavel Machek
2014-07-06 13:43 ` Pavel Machek
2014-07-06 18:29 ` Theodore Ts'o
2014-07-06 21:37 ` Pavel Machek
2014-07-07 1:00 ` Theodore Ts'o
2014-07-07 18:55 ` Pavel Machek
2014-07-07 23:18 ` 3.16-rc, ext4: oopses, OOMs after hard powerdown Pavel Machek
2014-07-07 23:21 ` ext4: media error but where? Theodore Ts'o
2014-06-27 8:23 ` ext4: total breakdown on USB hdd, 3.0 kernel Oliver Neukum
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=20140630134313.GA3753@thunk.org \
--to=tytso@mit.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).