All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre Etchemaite <petchema@concept-micro.com>
To: reiserfs-list@namesys.com
Subject: reiserfs3, rsync and hardlinks
Date: Sun, 6 Feb 2005 03:41:02 +0100	[thread overview]
Message-ID: <20050206034102.3956432d@polo.concept-micro.com> (raw)


	Hi all,

I'm using rsync to make a full backup of one box to another. Both are using
reiserfs 3.6.
The problem is that at the end of the backup, some pairs of unrelated files
(usually 3 or 4), are hardlinked together.

From what I've read in rsync mailing list archives, it probably means that
inode numbers are being reused while the backup is in progress.

Does that look plausible to you ?

And if it is, what can be done to significantly lower the probability of
inode number reuse over a short time ? The backup shouldn't take over 1
hour, the server stores around 570k files, but it's only a quite low traffic
IMAP server, so even with 32 bits inode numbers there's probably some room
for improvement.

I know a definitive answer would be to backup filesystem snapshots, but the
source server isn't currently using LVM1, and as far as I know snapshots
haven't been reimplemented yet for LVM2 :(

Best regards,
Pierre.

             reply	other threads:[~2005-02-06  2:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-06  2:41 Pierre Etchemaite [this message]
2005-02-06 19:18 ` reiserfs3, rsync and hardlinks David Masover
2005-02-06 21:55   ` Pierre Etchemaite
2005-02-07  5:33     ` David Masover
2005-02-08  9:42       ` mjt
2005-02-08 22:24         ` Hans Reiser
2005-02-07 10:22 ` Vladimir Saveliev
2005-02-07 20:50   ` Pierre Etchemaite
2005-02-07 21:32     ` Chris Mason
2005-02-08  5:53       ` David Masover
2005-02-08 22:14       ` Hans Reiser
2005-02-09  8:28         ` Pierre Etchemaite
2005-02-08 11:16     ` Vladimir Saveliev
2005-02-09  8:22       ` Pierre Etchemaite
2005-02-07 19:26 ` Hans Reiser

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=20050206034102.3956432d@polo.concept-micro.com \
    --to=petchema@concept-micro.com \
    --cc=reiserfs-list@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.