From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Cannot write file larger than 2TB on x86_64?
Date: Wed, 25 Jul 2007 09:16:13 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0707250916010.16609@p34.internal.lan> (raw)
In-Reply-To: <Pine.LNX.4.64.0707250914310.16609@p34.internal.lan>
Erm, unless this is an EXT3 limitation--oops..
On Wed, 25 Jul 2007, Justin Piszcz wrote:
> The kernel is 2.6.9-42.ELsmp on RHEL4 x86_64.
>
> servername$ dd if=/dev/zero of=4.8tb_file bs=1M count=4800000
> File size limit exceeded
> servername$ (stopped at 2TB)
>
> The 64bit should not need the option obviously, because it is 64bit, is this
> a b
> ug in the kernel?
>
> For 32bit:
> .config - Linux Kernel v2.6.22 Configuration
> ..............................................................................
> ..................... Support for Large Single Files ......................
> . CONFIG_LSF: .
> . .
> . Say Y here if you want to be able to handle very large files (bigger .
> . than 2TB), otherwise say N. .
> . .
> . If unsure, say Y. .
> .
>
> For 64bit:
> .config - Linux Kernel v2.6.22 Configuration
> ..............................................................................
> ............................... Block layer ...............................
> . Arrow keys navigate the menu. <Enter> selects submenus --->. .
> . Highlighted letters are hotkeys. Pressing <Y> includes, <N> excludes, .
> . <M> modularizes features. Press <Esc><Esc> to exit, <?> for Help, </> .
> . for Search. Legend: [*] built-in [ ] excluded <M> module < > .
> . ....................................................................... .
> . . --- Enable the block layer . .
> . . [ ] Support for tracing block io actions . .
> . . IO Schedulers ---> . .
> . .
> .
>
>
next prev parent reply other threads:[~2007-07-25 13:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-25 13:15 Justin Piszcz
2007-07-25 13:16 ` Justin Piszcz [this message]
2007-07-25 13:19 ` Justin Piszcz
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=Pine.LNX.4.64.0707250916010.16609@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--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
all inboxes | Powered by JetHome®