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: Thu, 26 Jun 2014 22:48:01 -0400 [thread overview]
Message-ID: <20140627024801.GG6826@thunk.org> (raw)
In-Reply-To: <20140626205049.GA11577@xo-6d-61-c0.localdomain>
On Thu, Jun 26, 2014 at 10:50:49PM +0200, Pavel Machek wrote:
>
> And for every bug in kernel, there's one in fsck: I did not expect it, but fsck actually
> suceeded, and marked fs as clean. But second fsck had issues with /lost+found...
I'd need the previous fsck transcript to have any idea what might have
happened. I'll note though you are using an ancient version of e2fsck
(1.41.12, and there have been a huge number of bug fixes since
May 2010....)
- Ted
next prev parent reply other threads:[~2014-06-27 2:48 UTC|newest]
Thread overview: 27+ 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 [this message]
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
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-07-04 19:17 ` Andreas Dilger
2014-07-04 20:33 ` Pavel Machek
2014-07-04 22:18 ` Andreas Dilger
2014-07-05 22:17 ` 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=20140627024801.GG6826@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 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.