From: William Park <opengeometry@yahoo.ca>
To: linux kernel <linux-kernel@vger.kernel.org>
Cc: "Peter T. Breuer" <ptb@it.uc3m.es>, dalecki@evision.ag
Subject: Re: blocks or KB? (was: .. current meaning of blk_size array)
Date: Wed, 14 Nov 2001 20:48:48 -0500 [thread overview]
Message-ID: <20011114204848.A3266@node0.opengeometry.ca> (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:
> > I at least am getting up to devicesizes at the 8TB range.
>
> If you are in that ballpark, then get the 64-bit blocknumber patch,
> and start testing/fixing, instead of complaining.
>
> Cheers, Andreas
Hi Andreas, can you give us URL for this 64-bit patch? I also want to
go past 1TB (512 * 2^31) filesystem size.
--
William Park, Open Geometry Consulting, <opengeometry@yahoo.ca>.
8 CPU cluster, NAS, (Slackware) Linux, Python, LaTeX, Vim, Mutt, Tin
next prev parent reply other threads:[~2001-11-15 1: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
2001-11-14 22:33 ` Scott Laird
2001-11-15 1:48 ` William Park [this message]
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=20011114204848.A3266@node0.opengeometry.ca \
--to=opengeometry@yahoo.ca \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox