From: Matti Aarnio <matti.aarnio@zmailer.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Bobby Hitt <bobhitt@bscnet.com>, linux-kernel@vger.kernel.org
Subject: Re: 2GB File limitation
Date: Fri, 28 Sep 2001 12:51:00 +0300 [thread overview]
Message-ID: <20010928125100.B1144@mea-ext.zmailer.org> (raw)
In-Reply-To: <013801c147e5$3330bec0$092cdb3f@bobathome> <Pine.LNX.4.33.0109281011010.2517-100000@localhost.localdomain>
In-Reply-To: <Pine.LNX.4.33.0109281011010.2517-100000@localhost.localdomain>; from mingo@elte.hu on Fri, Sep 28, 2001 at 10:13:09AM +0200
On Fri, Sep 28, 2001 at 10:13:09AM +0200, Ingo Molnar wrote:
> On Fri, 28 Sep 2001, Bobby Hitt wrote:
> > Is someone working on a way to overcome the 2GB file limitation in
> > Linux? I currently backup several servers using a dedicated hard drive
> > for the backups. Recently I saw one backup die saying the the file
> > size had been exceeded. I've never had good luck with tape backups,
> > yes they backup, but whenever I really need a file, it can't be
> > retrieved.
>
> file sizes up to ~ 2 TB are supported under the 2.4 kernel. (or 2.2 kernel
> + patches) Most utilities are updated to use O_LARGEFILE properly, in any
> recent 2.4-based Linux distribution. I regularly use 6-10 GB files.
Like Ingo says, most of modern distributions begin to work with
O_LARGEFILE properly, but still some utilities fail it.
Your older backup application program may fail it too.
The solution could be as simple as piping the backup material
into another program, which then pipes it out, e.g.:
'|dd bs=1M of=/backups/fileNNN'
> Ingo
/Matti Aarnio
next prev parent reply other threads:[~2001-09-28 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-28 6:17 Bobby Hitt
2001-09-28 7:33 ` Andreas Dilger
2001-09-28 8:13 ` Ingo Molnar
2001-09-28 9:51 ` Matti Aarnio [this message]
2001-09-28 13:02 ` M. Edward Borasky
2001-09-28 14:30 ` Michael H. Warfield
2001-09-28 20:17 ` Tim Moore
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=20010928125100.B1144@mea-ext.zmailer.org \
--to=matti.aarnio@zmailer.org \
--cc=bobhitt@bscnet.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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®