From: "Rob Turk" <r.turk@chello.nl>
To: linux-kernel@vger.kernel.org
Subject: Re: Stability of ReiserFS onj Kernel 2.4.x (sp. 2.4.[56]{-ac*}
Date: Sun, 15 Jul 2001 19:58:49 +0200 [thread overview]
Message-ID: <9islo5$na2$1@ncc1701.cistron.net> (raw)
In-Reply-To: <E15LopT-0004Cm-00@the-village.bc.nu> <3B51C864.C98B61DE@namesys.com>
"Hans Reiser" <reiser@namesys.com> wrote in message
news:cistron.3B51C864.C98B61DE@namesys.com...
>
> The limits for reiserfs and ext2 for kernels 2.4.x are the same (and they
are 2Tb not 1Tb). The
> limits are not in the individual filesystems. We need to have Linux go to
64 bit blocknumbers in
> 2.5.x, I am seeing a lot of customer demand for it. (Or we could use
scalable integers, which would
> be better.)
>
> Hans
> -
It appears to be 1TB. Just last week I tried a 1.1TB fibre RAID array, and
found several signed/unsigned issues. Fdisk was unable to work with the
array. This on Slackware 8.0 distribution with 2.4.6 kernel.
Rob
next prev parent reply other threads:[~2001-07-15 18:00 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-14 23:54 Stability of ReiserFS onj Kernel 2.4.x (sp. 2.4.[56]{-ac*} Adam Schrotenboer
2001-07-15 0:01 ` Thomas Zimmerman
2001-07-15 16:00 ` volodya
2001-07-15 16:08 ` Alexander Viro
2001-07-16 0:50 ` volodya
2001-07-16 0:54 ` Ragnar Kjørstad
2001-07-16 0:57 ` Alexander Viro
2001-07-16 1:22 ` volodya
2001-07-16 1:48 ` Ignacio Vazquez-Abrams
2001-07-15 16:33 ` Alan Cox
2001-07-15 16:44 ` Hans Reiser
2001-07-15 16:46 ` Alan Cox
2001-07-15 17:54 ` Hans Reiser
2001-07-15 18:17 ` Alan Cox
2001-07-16 13:27 ` Marco Colombo
2001-07-15 17:58 ` Rob Turk [this message]
2001-07-15 21:30 ` Daniel Phillips
2001-07-15 22:05 ` Hans Reiser
2001-07-15 22:18 ` Daniel Phillips
2001-07-16 0:22 ` Albert D. Cahalan
2001-07-16 12:49 ` Daniel Phillips
2001-07-17 19:40 ` Rob Landley
2001-07-16 17:19 ` Jussi Laako
2001-07-16 17:53 ` Daniel Phillips
2001-07-16 19:16 ` Hans Reiser
2001-07-16 21:00 ` Jussi Laako
2001-07-16 22:28 ` Daniel Phillips
2001-07-18 0:58 ` Dan Hollis
2001-07-16 4:39 ` Mike A. Harris
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='9islo5$na2$1@ncc1701.cistron.net' \
--to=r.turk@chello.nl \
--cc=linux-kernel@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