From: Benjamin LaHaise <bcrl@redhat.com>
To: "Peter T. Breuer" <ptb@it.uc3m.es>,
dalecki@evision.ag, linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: blocks or KB? (was: .. current meaning of blk_size array)
Date: Wed, 14 Nov 2001 16:49:57 -0500 [thread overview]
Message-ID: <20011114164957.A7587@redhat.com> (raw)
In-Reply-To: <3BF23D01.F7E879E8@evision-ventures.com> <200111142041.fAEKfBN15594@oboe.it.uc3m.es> <20011114141639.P5739@lynx.no>
In-Reply-To: <20011114141639.P5739@lynx.no>; from adilger@turbolabs.com on Wed, Nov 14, 2001 at 02:16:39PM -0700
On Wed, Nov 14, 2001 at 02:16:39PM -0700, Andreas Dilger wrote:
> Well, the rumor is wrong. There has always been a single-device 1TB/2TB
> limit in the kernel (2^31 or 2^32 * 512 byte sector size), and until
> recently it has not been a problem. To remove the problem Jens Axboe
> (I think, or Ben LaHaise, can't remember) has a patch to support 64-bit
> block counts and has been tested with > 2TB devices.
It was tested with a 10TB loopback raid, not a real device. Strangly,
nobody made any effort to test on real physical hardware (or offer any
hardware for me to test on ;-). The patch was against ~2.4.6 and will
need to get dusted off again soon.
-ben
--
Fish.
next prev parent reply other threads:[~2001-11-14 21:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 15:08 what is teh current meaning of blk_size? Peter T. Breuer
2001-11-13 18:51 ` blocks or KB? (was: .. current meaning of blk_size array) Peter T. Breuer
2001-11-14 9:44 ` Martin Dalecki
2001-11-14 20:41 ` Peter T. Breuer
2001-11-14 20:51 ` Martin Dalecki
2001-11-14 21:16 ` Andreas Dilger
2001-11-14 21:49 ` Benjamin LaHaise [this message]
2001-11-14 22:33 ` Scott Laird
2001-11-15 1:48 ` William Park
2001-11-15 4:58 ` Andreas Dilger
2001-11-15 5:34 ` William Park
2001-11-15 5:55 ` Andreas Dilger
2001-11-15 10:42 ` Anton Altaparmakov
2001-11-15 12:35 ` Peter T. Breuer
2001-11-15 18:31 ` William Park
2001-11-15 20:19 ` Andreas Dilger
2001-11-15 22:04 ` blocks or KB? William Park
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=20011114164957.A7587@redhat.com \
--to=bcrl@redhat.com \
--cc=dalecki@evision.ag \
--cc=linux-kernel@vger.kernel.org \
--cc=ptb@it.uc3m.es \
/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.