public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: Pavel Machek <pavel@suse.cz>
Cc: adefacc@tin.it, linux-kernel@vger.kernel.org,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: Confirmation request about new 2.4.x. kernel limits
Date: Tue, 9 Jan 2001 14:03:34 +0000	[thread overview]
Message-ID: <20010109140334.C4284@redhat.com> (raw)
In-Reply-To: <3A546385.C50B1092@tin.it> <20010105234604.C301@bug.ucw.cz>
In-Reply-To: <20010105234604.C301@bug.ucw.cz>; from pavel@suse.cz on Fri, Jan 05, 2001 at 11:46:04PM +0100

Hi,

On Fri, Jan 05, 2001 at 11:46:04PM +0100, Pavel Machek wrote:
> 
> > Max. file size:	 		1 TB	(?)
> > Max. file system size:		2 TB	(?)
> 
> Again, maybe on i386 with ext2.

Actually, the 2TB limit affects all architectures, as we assume that
block indexes fit into 32 bits.  Blocks are passed around as unsigned
longs in some cases, but even on 64-bit machines that doesn't help us
as the limit still persists in the filesystem (32-bit block numbers)
and device drivers (ints and 4-byte sector numbers used when
generating SCSI commands).

Auditing the whole driver path to allow 64-bit block numbers, and
adding the logic to generate the 5th sector address byte in the scsi
command when we're doing 10-byte commands, are all possible extensions
for 2.5.  For now, though, the 2TB device limit is with us for all
architectures and all filesystems on 2.4.

--Stephen
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-09 14:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-04 11:50 Confirmation request about new 2.4.x. kernel limits A.D.F.
2001-01-04 11:23 ` Tigran Aivazian
2001-01-04 11:50 ` Anton Blanchard
2001-01-05 22:46 ` Pavel Machek
2001-01-09 14:03   ` Stephen C. Tweedie [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-01-09  4:11 Venkatesh Ramamurthy
2001-01-09 12:21 ` Matti Aarnio
2001-01-09 16:27   ` Tim Wright
2001-01-09 16:44     ` Andi Kleen
2001-01-09 16:50       ` Tim Wright
2001-01-10 13:16     ` Kurt Garloff
2001-01-09 14:05 ` Stephen C. Tweedie
2001-01-09 15:15 Venkatesh Ramamurthy
2001-01-09 15:51 ` Andi Kleen
2001-01-09 17:35 Venkatesh Ramamurthy
2001-01-09 17:47 ` Andi Kleen
2001-01-09 18:00 Venkatesh Ramamurthy

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=20010109140334.C4284@redhat.com \
    --to=sct@redhat.com \
    --cc=adefacc@tin.it \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    /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