All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Christoph Anton Mitterer <calestyo@scientia.org>,
	linux-btrfs@vger.kernel.org
Subject: Re: empty directory from previous subvolume in a snapshot is not sent|received
Date: Fri, 23 Jun 2023 07:55:07 +0300	[thread overview]
Message-ID: <d7905c54-e8bb-882c-8e7c-048dfe865ee2@gmail.com> (raw)
In-Reply-To: <bbccd0204d2951f54f4303aca3af1b6dab2c3108.camel@scientia.org>

On 22.06.2023 19:09, Christoph Anton Mitterer wrote:
> 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.

It is not directory. It is "orphan subvolume graft point" for the lack 
of better term.

tw:/mnt # btrfs subvolume create ./data/pictures
Create subvolume './data/pictures'
tw:/mnt # btrfs subvolume snapshot data/ snap1
Create a snapshot of 'data/' in './snap1'
tw:/mnt # ll snap1
total 0
drwxr-xr-x 1 root root 0 Jun 23 07:53 pictures
tw:/mnt # touch snap1/pictures/foo
touch: cannot touch 'snap1/pictures/foo': Permission denied
tw:/mnt #


> 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.


  reply	other threads:[~2023-06-23  4:55 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
2023-06-23  4:55     ` Andrei Borzenkov [this message]
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=d7905c54-e8bb-882c-8e7c-048dfe865ee2@gmail.com \
    --to=arvidjaar@gmail.com \
    --cc=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 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.