From: Thornton Prime <theoszi@gmail.com>
To: fluca1978@infinito.it
Cc: linux-admin@vger.kernel.org
Subject: Re: 2GB max file size
Date: Tue, 29 Mar 2005 07:00:58 -0800 [thread overview]
Message-ID: <2d7eccf50503290700374e0bbf@mail.gmail.com> (raw)
In-Reply-To: <200503291650.11908.fluca1978@infinito.it>
On Tue, 29 Mar 2005 16:50:11 +0200, Luca Ferrari <fluca1978@infinito.it> wrote:
> I think there must be a solution for that "roof" of 2 GB for a single file. It
> will be great, since my backups are often bigger than 2 GB so I cannot
> zip/tar them in a single file. Any suggestion?
The solution was implemented quite some time ago, I can't even recall
how long ago. I regularly create 10G to 200G files on Linux with
standard tools.
What kernel/glibc/filesystem are you running?
thornton
next prev parent reply other threads:[~2005-03-29 15:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-29 14:50 2GB max file size Luca Ferrari
2005-03-29 15:00 ` Thornton Prime [this message]
[not found] <5.2.1.1.0.20050329160147.049ed668@127.0.0.1>
2005-03-29 15:33 ` Luca Ferrari
2005-03-29 16:02 ` Thornton Prime
2005-04-02 12:35 ` Glynn Clements
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=2d7eccf50503290700374e0bbf@mail.gmail.com \
--to=theoszi@gmail.com \
--cc=fluca1978@infinito.it \
--cc=linux-admin@vger.kernel.org \
--cc=thornton@yoyoweb.com \
/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;
as well as URLs for NNTP newsgroup(s).