From: Ted Ts'o <tytso@mit.edu>
To: Daniel Taylor <Daniel.Taylor@wdc.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: Repost (from LKML): EXT3 FS and 64K blocks error
Date: Fri, 9 Jul 2010 20:26:11 -0400 [thread overview]
Message-ID: <20100710002611.GA17032@thunk.org> (raw)
In-Reply-To: <469D2D911E4BF043BFC8AD32E8E30F5B24AEEE@wdscexbe07.sc.wdc.com>
On Fri, Jul 09, 2010 at 03:32:22PM -0700, Daniel Taylor wrote:
> We're switching to ext4. I just thought someone might want to take
> a look at the error message. I can do some more testing, next
> week, if there are suggestions of what to try.
I can try to dig up the patch we used to fix 64k block sizes for ext4,
and backport it to ext3, but to be honest I'm pretty overbooked
already as it is, and in general we've been trying to keep ext3
stable, which means in practice, bug fixes only. The question is
whether 64k blocksize support is considered a bug fix or a new
feature.... so if you're switching to ext4 anyway, I'd probably just
not bother trying to fix it for ext3...
- Ted
next prev parent reply other threads:[~2010-07-10 0:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-09 0:10 Repost (from LKML): EXT3 FS and 64K blocks error Daniel Taylor
2010-07-09 12:03 ` Theodore Tso
2010-07-09 22:32 ` Daniel Taylor
2010-07-10 0:26 ` Ted Ts'o [this message]
2010-07-10 22:14 ` Andreas Dilger
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=20100710002611.GA17032@thunk.org \
--to=tytso@mit.edu \
--cc=Daniel.Taylor@wdc.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