From: Christoph Hellwig <hch@infradead.org>
To: Mark Harmstone <mark@harmstone.com>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-btrfs@vger.kernel.org, framstag@rus.uni-stuttgart.de
Subject: Re: restic backup with btrfs /
Date: Mon, 30 Jun 2025 06:57:20 -0700 [thread overview]
Message-ID: <aGKXwNaNgWM24KHh@infradead.org> (raw)
In-Reply-To: <5b928de3-579a-402d-bb75-e93b473de929@harmstone.com>
On Mon, Jun 30, 2025 at 02:53:23PM +0100, Mark Harmstone wrote:
> > .. because it isn't. btrfs is the buggy one here breaking the old
> > Unix tradition also (somewhat vaguely) encoded in Posix that st_dev must
> > not changed except at a mount point.
>
> I know. But if POSIX assumes that every inode has a unique combination of
> st_dev and st_ino, and that both are 64 bits, that's incompatible with the
> design of btrfs.
I know, we had a few discussions on that.
next prev parent reply other threads:[~2025-06-30 13:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-28 17:33 restic backup with btrfs / Ulli Horlacher
2025-06-30 10:07 ` Mark Harmstone
2025-06-30 13:41 ` Christoph Hellwig
2025-06-30 13:53 ` Mark Harmstone
2025-06-30 13:57 ` Christoph Hellwig [this message]
2025-06-30 17:30 ` Ulli Horlacher
2025-06-30 19:16 ` Ulli Horlacher
2025-07-03 8:00 ` Robert Krig
2025-07-04 9:39 ` Ulli Horlacher
2025-07-07 13:46 ` Ulli Horlacher
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=aGKXwNaNgWM24KHh@infradead.org \
--to=hch@infradead.org \
--cc=framstag@rus.uni-stuttgart.de \
--cc=linux-btrfs@vger.kernel.org \
--cc=mark@harmstone.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox