From: Lukas Straub <lukasstraub2@web.de>
To: Andy Smith <andy@strugglers.net>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: "Too many links (31)" issue
Date: Thu, 3 Feb 2022 22:15:06 +0000 [thread overview]
Message-ID: <20220203221506.212e72e8@gecko> (raw)
In-Reply-To: <20220203163108.ipdv3yxbe7eb6vc4@bitfolk.com>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On Thu, 3 Feb 2022 16:31:08 +0000
Andy Smith <andy@strugglers.net> wrote:
> Hi,
>
> I have a host with an xfs filesystem on it, with about 25 million
> files. It contains an rsnapshot backup that has been aggressively
> deduplicated by means of hardlinks and there's probably only about 7
> million unique files on there.
>
> I'm trying to rsync it to a different host into a btrfs filesystem,
> but part way through the rsync I get a "Too many links (31)" error:
>
> rsync: [generator] link "/data/backup/rsnapshot/daily.0/chacha/var/lib/dpkg/info/.apt-utils.postrm.0" => daily.0/backup1/var/lib/dpkg/info/libpango1.0-0.postrm failed: Too many links (31)
> Hlink node data for 219191 already has path=daily.0/backup1/var/lib/dpkg/info/libpango1.0-0.postrm (daily.0/chacha/var/lib/dpkg/info/apt-utils.postrm)
> rsync error: errors with program diagnostics (code 13) at hlink.c(539) [generator=3.2.3]
>
> I searched around on this topic and found hits from 10 years ago
> about maximum hardlinks per directory and being dependent upon
> length of file path. Is that still relevant today?
>
> [...]
>
> Is there anything I can do to get this working?
Hello, Have you tried the "extended_iref" mount option?
--
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-02-03 22:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-03 16:31 "Too many links (31)" issue Andy Smith
2022-02-03 22:15 ` Lukas Straub [this message]
2022-02-03 22:27 ` Andy Smith
2022-02-04 14:30 ` Filipe Manana
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=20220203221506.212e72e8@gecko \
--to=lukasstraub2@web.de \
--cc=andy@strugglers.net \
--cc=linux-btrfs@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