From: Ted Ts'o <tytso@mit.edu>
To: Amir Goldstein <amir73il@gmail.com>
Cc: Ric Wheeler <rwheeler@redhat.com>,
Rogier Wolff <R.E.Wolff@bitwizard.nl>,
Con Kolivas <kernel@kolivas.org>,
adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org
Subject: Re: Regular ext4 error warning with HD in USB dock
Date: Fri, 7 Jan 2011 00:26:13 -0500 [thread overview]
Message-ID: <20110107052613.GE2857@thunk.org> (raw)
In-Reply-To: <AANLkTimAe-p1-ApmnueybQY474J3_G9JL+8WJ2WTn+04@mail.gmail.com>
Am I missing something? The kernel stores up to 3k worth of data, on
a 4k block file system. Whereas e2fsck patch blindly assume 2k worhth
of data regardless of the block size. The kernel patch looks ok, but
the e2fsprogs patch seems badly broken....
- Ted
next prev parent reply other threads:[~2011-01-07 5:26 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-27 22:53 Regular ext4 error warning with HD in USB dock Con Kolivas
2010-12-28 2:53 ` Ted Ts'o
2010-12-28 8:19 ` Rogier Wolff
2010-12-28 9:09 ` Con Kolivas
2010-12-28 10:30 ` Amir Goldstein
2010-12-28 10:30 ` Amir Goldstein
2011-01-01 17:20 ` Ric Wheeler
2011-01-02 19:23 ` Amir Goldstein
2011-01-07 5:26 ` Ted Ts'o [this message]
2011-01-07 19:41 ` Amir Goldstein
2011-01-07 21:07 ` Amir Goldstein
2011-01-07 22:12 ` Amir Goldstein
2011-01-08 20:28 ` Amir Goldstein
2011-01-08 8:05 ` Rogier Wolff
2011-01-08 20:06 ` Amir Goldstein
2011-01-08 22:00 ` Ted Ts'o
2011-01-09 8:12 ` Rogier Wolff
2011-01-09 14:58 ` Ted Ts'o
2011-01-10 7:45 ` Andreas Dilger
2011-01-10 8:49 ` Rogier Wolff
2011-01-07 5:28 ` Ted Ts'o
2011-01-07 19:43 ` Amir Goldstein
2011-01-07 20:39 ` Amir Goldstein
2010-12-28 14:15 ` Ted Ts'o
2010-12-28 10:41 ` torn5
[not found] ` <4D19BEF1.9010708-9AbUPqfR1/2XDw4h08c5KA@public.gmane.org>
2010-12-28 14:32 ` Ted Ts'o
2010-12-28 14:32 ` Ted Ts'o
2010-12-28 15:02 ` Ben Pfaff
2010-12-28 15:20 ` torn5
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=20110107052613.GE2857@thunk.org \
--to=tytso@mit.edu \
--cc=R.E.Wolff@bitwizard.nl \
--cc=adilger.kernel@dilger.ca \
--cc=amir73il@gmail.com \
--cc=kernel@kolivas.org \
--cc=linux-ext4@vger.kernel.org \
--cc=rwheeler@redhat.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.