From: Bryan O'Sullivan <bos@serpentine.com>
To: Stephan van Hienen <raid@a2000.nu>
Cc: linux-raid@vger.kernel.org, ext2-devel@lists.sourceforge.net,
tbm@a2000.nu
Subject: Re: [Ext2-devel] Re: fsck out of memory
Date: 11 Feb 2003 12:04:17 -0800 [thread overview]
Message-ID: <1044993857.6640.7.camel@plokta.s8.com> (raw)
In-Reply-To: <1044973982.1980.29.camel@sisko.scot.redhat.com>
On Tue, 2003-02-11 at 06:33, Stephen C. Tweedie wrote:
> I've no idea. Ben has some lb patches up at
>
> http://people.redhat.com/bcrl/lb/
>
> but there's nothing broken out against the latest lbd diffs.
Ugh, that stuff is ancient.
Peter Chubb has a backport of his (very thorough) 2.5 patch to support
large block devices on 32-bit platforms, against much newer kernels
(e.g. 2.4.20) than Ben's stuff. His site seems to be down, but you
should be able to get it from somewhere under
http://www.gelato.unsw.edu.au/~peterc/
I haven't used Peter's patch, but a similar patch, developed
independently, definitely allows ext3 filesystems of up to 8TB in size
to work fine on x86, under 2.4.
The nominal limit on device/filesystem size looks to be 16TB on a 32-bit
platform, but there are dozens of sign truncation errors throughout the
VFS and block layers that are unlikely to get fixed. Hence, 8TB it is.
<b
next prev parent reply other threads:[~2003-02-11 20:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 15:17 fsck out of memory kernel
2003-02-07 15:41 ` Wim Vinckier
2003-02-07 15:50 ` kernel
2003-02-07 16:09 ` Wim Vinckier
2003-02-07 16:15 ` Stephan van Hienen
2003-02-07 16:20 ` Wim Vinckier
2003-02-07 17:08 ` Stephan van Hienen
2003-02-07 16:16 ` Wim Vinckier
2003-02-07 17:07 ` Stephan van Hienen
2003-02-07 17:28 ` Andreas Dilger
2003-02-09 10:08 ` Stephan van Hienen
2003-02-09 10:32 ` Stephan van Hienen
2003-02-09 20:08 ` Peter Chubb
2003-02-10 11:28 ` Stephan van Hienen
2003-02-09 20:31 ` Andreas Dilger
2003-02-10 12:01 ` Stephan van Hienen
[not found] ` <3E479CC7.B170D5C7@aitel.hist.no>
2003-02-11 16:14 ` Re:2TB+ fs ext3 (was fsck out of memory) Stephan van Hienen
2003-02-10 22:44 ` [Ext2-devel] Re: fsck out of memory Stephen C. Tweedie
2003-02-11 13:11 ` Stephan van Hienen
2003-02-11 14:33 ` Stephen C. Tweedie
2003-02-11 20:04 ` Bryan O'Sullivan [this message]
2003-02-11 20:21 ` Matthew Wilcox
2003-02-11 20:32 ` Re:2TB+ fs ext3 (was fsck out of memory) Stephan van Hienen
2003-02-07 17:24 ` fsck out of memory Andreas Dilger
[not found] <5250726@toto.iv>
2003-02-13 3:30 ` [Ext2-devel] " Peter Chubb
2003-02-13 4:01 ` Randy.Dunlap
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=1044993857.6640.7.camel@plokta.s8.com \
--to=bos@serpentine.com \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-raid@vger.kernel.org \
--cc=raid@a2000.nu \
--cc=tbm@a2000.nu \
/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).