From: Christoph Anton Mitterer <calestyo@scientia.net>
To: Anand Jain <anand.jain@oracle.com>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: kernel trace, (nearly) every time on send/receive
Date: Mon, 02 Dec 2019 04:30:17 +0100 [thread overview]
Message-ID: <5cea01b65a3cfe773300f69d5847cdc457ab49d1.camel@scientia.net> (raw)
In-Reply-To: <768283ac-99c5-0fd1-2acb-e504cbb1f3fd@oracle.com>
Hey Anand.
Thanks for looking into this.
On Mon, 2019-12-02 at 10:58 +0800, Anand Jain wrote:
> Looks like ORPHAN_CLEANUP_DONE is not set on the root.
>
> WARN_ON(send_root->orphan_cleanup_state !=
> ORPHAN_CLEANUP_DONE);
>
> ORPHAN_CLEANUP_DONE is set unless it is a readonly FS, which I doubt
> is,
> (can be checked using btrfs inspect duper-super <dev>) because you
> are
> creating the snapshot for the send.
I should perhaps add, that there are two btrfs filesystems involved
here:
The first is basically the master, having several snapshots including
all + one newer which is missing from the second (which is basically a
backup of the master).
So it's about:
/master# btrfs send -p already-on-copy newer-snapshot | btrfs receive /copy/snapshots/ ;
In fact /master is mounted ro only here, whereas /copy is of course
mounted rw.
Since nothing should be changed on /master I assumed it would be ok to
have it mounted ro.
> btrfs check --readonly might tell
> us more about the issue.
I cannot do this right now since I'll be on some diving vacation for ~2
weeks,... but since --readonly is the standard behaviour (i.e. same
without --readonly) I'm pretty sure that a fsck (which I always do
after each snapshot to the /copy) brought now visible errors.
Does the whole thing imply any corruption to any of the two
filesystems... or is it just a "cosmetic" issue?
Cheers,
Chris
next prev parent reply other threads:[~2019-12-02 3:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 22:27 kernel trace, (nearly) every time on send/receive Christoph Anton Mitterer
2019-12-02 2:58 ` Anand Jain
2019-12-02 3:30 ` Christoph Anton Mitterer [this message]
2019-12-02 4:37 ` Anand Jain
2019-12-02 13:04 ` 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=5cea01b65a3cfe773300f69d5847cdc457ab49d1.camel@scientia.net \
--to=calestyo@scientia.net \
--cc=anand.jain@oracle.com \
--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;
as well as URLs for NNTP newsgroup(s).