From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Dennis Katsonis <dennisk@netspace.net.au>
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Incremental receive completes succesfully despite missing files
Date: Wed, 23 Jan 2019 14:25:03 +0300 [thread overview]
Message-ID: <CAA91j0VSd=uC7ROT2+JsRszzAXWz+ti-Kf3hyw+aVS03sdn95g@mail.gmail.com> (raw)
In-Reply-To: <3cfb98e1-92d4-150c-445c-9357cec9adca@netspace.net.au>
On Wed, Jan 23, 2019 at 1:45 PM Dennis Katsonis <dennisk@netspace.net.au> wrote:
> I think my previous e-mail did not go through. Basically, if it is
> assumed that a btrfs-receive operation will result in a subvolume which
> matches the source file for file, then this assumption or expectation
> won't be met if one deletes files from the subvolume at the receiving
> end which is going to be referred to as the parent.
>
This is oxymoron. btrfs send/receive apply to read-only subvolumes.
You are not able to modify them. As soon as you remove read-only bit,
you are fully responsible for consequences.
> This can happen inadvertently,
It cannot. You do not inadvertently make subvolume read-write. And if
you do, you are expected to know what you are doing.
That said, better if btrfs did not allow flipping read-only bit in the
first place.
> or even through filesystem corruption
> (which I experienced).
>
And if corruption happened after applying changes? End result in the
same. Of course it would be perfect if btrfs could notice and warn
you, I just do not see how it can realistically be implemented.
next prev parent reply other threads:[~2019-01-23 11:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 10:25 Incremental receive completes succesfully despite missing files Dennis K
2019-01-20 14:04 ` Andrei Borzenkov
2019-01-21 22:23 ` Chris Murphy
2019-01-22 4:36 ` Chris Murphy
2019-01-22 4:54 ` Chris Murphy
2019-01-22 6:00 ` Remi Gauvin
2019-01-22 6:28 ` Chris Murphy
2019-01-22 17:57 ` Andrei Borzenkov
2019-01-22 19:37 ` Chris Murphy
2019-01-22 19:45 ` Hugo Mills
2019-01-23 10:44 ` Dennis Katsonis
2019-01-23 11:25 ` Andrei Borzenkov [this message]
2019-01-23 13:52 ` Dennis Katsonis
2019-01-23 18:17 ` Andrei Borzenkov
2019-01-23 15:25 ` Hans van Kranenburg
2019-01-23 15:32 ` Nikolay Borisov
2019-01-23 16:23 ` Hans van Kranenburg
2019-01-24 10:40 ` Dennis K
2019-01-24 17:22 ` Chris Murphy
2019-01-26 2:43 ` Dennis Katsonis
2019-01-26 23:09 ` Chris Murphy
2019-01-27 1:58 ` Dennis Katsonis
2019-01-23 15:40 ` Remi Gauvin
2019-01-23 16:59 ` Hans van Kranenburg
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='CAA91j0VSd=uC7ROT2+JsRszzAXWz+ti-Kf3hyw+aVS03sdn95g@mail.gmail.com' \
--to=arvidjaar@gmail.com \
--cc=dennisk@netspace.net.au \
--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.