All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Leiber <paul@onlineschubla.de>
To: Roman Mamedov <rm@romanrm.net>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: AW: Parent transid verify failed (and more): BTRFS for data storage in Xen VM setup
Date: Sat, 10 Apr 2021 21:28:44 +0000	[thread overview]
Message-ID: <FRYP281MB0582CFDA373D3F760D75F592B0729@FRYP281MB0582.DEUP281.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <20210410194842.71f49059@natsu>

Von: Roman Mamedov <rm@romanrm.net>
Gesendet: Samstag, 10. April 2021 16:49
> 
> On Sat, 10 Apr 2021 13:38:57 +0000
> Paul Leiber <paul@onlineschubla.de> wrote:
> 
> > e) Perhaps it is wrong to mount the BTRFS root first in the Dom0 and then
> accessing the subvolumes in the DomU?
> 
> Absolutely O.o
> 
> Subvolumes are very much like directories, not any kind of subpartitions.
> 
> Imagine you'd try to use the same ext4 from the host and from a VM guest,
> saying "but they both store their data in separate folders!"

Thank you for your quick reply. What you write could indeed explain my situation. Of course, I should have thought of that earlier. Well, I wanted to learn, and learning I am... I will set up the partition (again! :-) and pay care to not having duplicate mounts on different VMs. I will give feedback in a couple of days.

Best regards,

Paul



  reply	other threads:[~2021-04-10 21:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 13:38 Parent transid verify failed (and more): BTRFS for data storage in Xen VM setup Paul Leiber
2021-04-10 14:48 ` Roman Mamedov
2021-04-10 21:28   ` Paul Leiber [this message]
2021-04-10 23:06   ` Chris Murphy
2021-04-11  4:50     ` Andrei Borzenkov
2021-04-11  7:10     ` Roman Mamedov
2021-04-11 20:43       ` Adam Borowski
2021-04-26 20:23   ` AW: " Paul Leiber

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=FRYP281MB0582CFDA373D3F760D75F592B0729@FRYP281MB0582.DEUP281.PROD.OUTLOOK.COM \
    --to=paul@onlineschubla.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rm@romanrm.net \
    /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.