From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Jamie Lokier <jamie@shareable.org>
Cc: Pavel Machek <pavel@ucw.cz>,
Sytse Wielinga <s.b.wielinga@student.utwente.nl>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH for testing] cow behaviour for hard links
Date: Mon, 15 Mar 2004 11:27:04 +0100 [thread overview]
Message-ID: <20040315102704.GA16615@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20040315074558.GA7188@mail.shareable.org>
On Mon, 15 March 2004 07:45:58 +0000, Jamie Lokier wrote:
> Pavel Machek wrote:
> > > Or did you mean the problem of tar backups growing *much* larger than
> > > the real filesystem? Yes, tar becomes useless for backups then. :)
> >
> > Yep, this is what I meant.
>
> A different but related problem: rsync cannot backup my kernel
> development directory from one hard disk to another, because it
> contains lots of kernel trees mostly hard linked to each other. rsync
> falls over, trying to keep track of the roughly half a million links.
>
> You might see similar problems trying to backup a strongly "copyfile"'d
> filesystems.
And both are easily fixable, if you don't mind using 16 bytes of RAM
per inode. At least for rsync this should be a piece of cake compared
to the amount of memory already used. :)
Jörn
--
When in doubt, use brute force.
-- Ken Thompson
next prev parent reply other threads:[~2004-03-15 10:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-10 19:34 Jörn Engel
2004-03-10 19:35 ` [Program " Jörn Engel
2004-03-10 21:34 ` [PATCH " Jamie Lokier
2004-03-10 22:17 ` Jörn Engel
2004-03-10 23:07 ` Sytse Wielinga
2004-03-10 23:46 ` Sytse Wielinga
2004-03-12 17:48 ` Sytse Wielinga
2004-03-12 18:18 ` Jörn Engel
2004-03-12 18:29 ` Jörn Engel
2004-03-13 13:43 ` Pavel Machek
2004-03-13 19:48 ` Jörn Engel
2004-03-13 21:03 ` Pavel Machek
2004-03-15 7:45 ` Jamie Lokier
2004-03-15 10:27 ` Jörn Engel [this message]
2004-03-13 22:14 ` Jörn Engel
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=20040315102704.GA16615@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=jamie@shareable.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=s.b.wielinga@student.utwente.nl \
/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®