From: James <james@piku.org.uk>
To: "'linux-admin@vger.kernel.org'" <linux-admin@vger.kernel.org>
Subject: Re: tar / backup solutions
Date: Mon, 29 Apr 2002 20:25:42 +0100 [thread overview]
Message-ID: <20020429192542.GV23141@piku.org.uk> (raw)
In-Reply-To: <20020429182003.40701.qmail@web12804.mail.yahoo.com>
On Mon, Apr 29, 2002 at 11:20:03AM -0700, Christopher Slater wrote:
| I thought that gtar allowed bigger than 2G tarballs. It could be a
| filesystem problem. I think the default in some Unixes is for
| "nolargefiles". That is, no files larger than 2G. You might check
| that you're not running into that.
ext2 did have a 2GB limit. I think it's gone away now. I run ReiserFS
and I believe that can cope with big files.
| One other option would be to break your backup into 2G chunks. Say,
| backup /home into /backup/fullbackup_home.tar.gz, etc...
This would be a safer idea anyway. Should your large multi-gig tarfile
get corrupt, you're stuffed. But if only your home.tar file got
corrupt, you've not lost your entire backup.
There's now the question of whether you should back up to your
harddrive... Expend some cash on a DAT drive, it's worth it. It's no
good having backups on disk if your harddrive dies.
--
I am not my long-lost twin
6AD6 865A BF6E 76BB 1FC2 | www.piku.org.uk/public-key.asc
E4C4 DEEA 7D08 D511 E149 | www.piku.org.uk wnzrf@cvxh.bet.hx (rot13'd)
next prev parent reply other threads:[~2002-04-29 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-29 18:01 tar / backup solutions Walsh, Ed
2002-04-29 18:20 ` Christopher Slater
2002-04-29 19:25 ` James [this message]
2002-04-29 21:56 ` New Harddrive problems omland
2002-04-29 22:16 ` James
2002-05-23 20:56 ` Subnetting Question omland
2002-05-23 21:00 ` Gary E. Miller
2002-05-24 5:40 ` ATI AR320 Horia Chirculescu
2002-05-23 21:01 ` Subnetting Question Teodor Iacob
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=20020429192542.GV23141@piku.org.uk \
--to=james@piku.org.uk \
--cc=linux-admin@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;
as well as URLs for NNTP newsgroup(s).