Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: Christoph Anton Mitterer <calestyo@scientia.org>
To: linux-btrfs@vger.kernel.org
Subject: empty directory from previous subvolume in a snapshot is not sent|received
Date: Thu, 22 Jun 2023 15:34:26 +0200	[thread overview]
Message-ID: <ea6099a3cff73c20da032afaaeb446c0b12ec1da.camel@scientia.org> (raw)

Hey.

Not sure whether this is a bug or expected.

On my btrfs I have subvolumes like:
  data/
  2023-06-21/
where e.g. data/ contains the root filesystem and 2023-06-21/ is a ro-
snapshot thereof.


When I created 2023-06-21/ from data/, the latter contained another
(rw-)subvolume data/pictures/, which I've deleted (actually: moved out
the files back to data/ and rmdir-ed the now empty subvol... or maybe I
did btrfs subvolume delete - not sure anymore) again after creating the
snapshot.


Now 2023-06-21/ contains an empty (non-subvolume) 2023-06-21/pictures/,
which is expected.


Today I've send|received 2023-06-21/ to another btrfs (at that point,
the original data/pictures/ subvolume was already gone), and diff -qr -
-no-dereference-ed the two afterwards.

Outcome (apart from "differing" files/sockets/block/char special files)
is that the target doesn't contain the empty pictures/ dir.


Not a big problem for me,... but is this expected or some kind of
strange bug?


Thanks,
Chris.

             reply	other threads:[~2023-06-22 13:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-22 13:34 Christoph Anton Mitterer [this message]
2023-06-22 15:22 ` empty directory from previous subvolume in a snapshot is not sent|received Andrei Borzenkov
2023-06-22 16:09   ` Christoph Anton Mitterer
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=ea6099a3cff73c20da032afaaeb446c0b12ec1da.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