From: Christoph Anton Mitterer <calestyo@scientia.org>
To: linux-btrfs@vger.kernel.org
Subject: Re: empty directory from previous subvolume in a snapshot is not sent|received
Date: Thu, 22 Jun 2023 18:09:45 +0200 [thread overview]
Message-ID: <bbccd0204d2951f54f4303aca3af1b6dab2c3108.camel@scientia.org> (raw)
In-Reply-To: <9fd09e52-e77e-415b-bd95-9c58dde263d0@gmail.com>
On Thu, 2023-06-22 at 18:22 +0300, Andrei Borzenkov wrote:
> I think it is expected. btrfs does not support either recursive
> snapshots or recursive send so "btrfs send" skips directory entry
> that
> points to subvolume root.
Well it's clear that the sub-volume is not contained in the snapshot or
sent.
But in the snapshot (on the original fs) I have the empty directory
from the subvolume that was not recursively snapshotted.
Shouldn't that be just a plain empty directory... and thus be
sent|received (as empty directory) when I send|receive the snapshot?
Cheers,
Chris.
next prev parent reply other threads:[~2023-06-22 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 13:34 empty directory from previous subvolume in a snapshot is not sent|received Christoph Anton Mitterer
2023-06-22 15:22 ` Andrei Borzenkov
2023-06-22 16:09 ` Christoph Anton Mitterer [this message]
2023-06-23 4:55 ` Andrei Borzenkov
2023-06-23 18:10 ` Christoph Anton Mitterer
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=bbccd0204d2951f54f4303aca3af1b6dab2c3108.camel@scientia.org \
--to=calestyo@scientia.org \
--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