From: Chris Wedgwood <cw@f00f.org>
To: Anton Petrusevich <casus@att-ltd.biz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ftruncate64
Date: Wed, 3 Mar 2004 02:08:30 -0800 [thread overview]
Message-ID: <20040303100830.GA16569@dingdong.cryptoapps.com> (raw)
In-Reply-To: <200402260523.10394.casus@att-ltd.biz>
On Thu, Feb 26, 2004 at 05:23:10AM +0600, Anton Petrusevich wrote:
> ftruncate64(1, 2199023255552) = -1 EFBIG (File too large)
Depends on your fs, some fs's will allow you to create much larger
files that others:
cw@pain:~$ truncate -c -s100t big-file
cw@pain:~$ ls -lh big-file
-rw-r--r-- 1 cw cw 100T Mar 3 02:05 big-file
Note, you might need a 64-bit system to be able to write to all of
that because the index into the buffer-cache is an unsigned long. For
me on my notebook I can't write past 8T.
--cw
next prev parent reply other threads:[~2004-03-03 10:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-25 23:23 ftruncate64 Anton Petrusevich
2004-03-03 10:08 ` Chris Wedgwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-25 23:27 ftruncate64 Anton Petrusevich
[not found] <1tgNg-8o9-5@gated-at.bofh.it>
[not found] ` <1vBDZ-48V-7@gated-at.bofh.it>
2004-03-03 21:42 ` ftruncate64 Bill Davidsen
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=20040303100830.GA16569@dingdong.cryptoapps.com \
--to=cw@f00f.org \
--cc=casus@att-ltd.biz \
--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