All of lore.kernel.org
 help / color / mirror / Atom feed
From: carlo von lynX <lynX@time.to.get.psyced.org>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Impossible to mount two different copies of the same btrfs
Date: Thu, 27 Aug 2015 20:44:15 +0200	[thread overview]
Message-ID: <20150827184415.GA31439@lo.psyced.org> (raw)
In-Reply-To: <20150827175947.GL23769@carfax.org.uk>

Thanks for the feedback. I thought I had bumped into a totally excentric
use case but really I am making a most average beginner's mistake. I
should have noticed when my thinking was in terms of rsync. btrfs-tune
would be the hack I first thought of, but I realize that is the wimp's
way to go.

So now I'm trying it the btrfs way. I made a fresh snapshot of the
current state, created a send file (one gig! ;)) from the previous
snapshot. Then I unmounted the source fs and mounted the dest copy.
Unfortunately I cannot 'btrfs receive' since I didn't have read-only
snapshots and making them from existing ones does not yield the same
parent ids.

Looks like I have to format a new target btrfs and start anew with
a full snapshot send... then at least I get to use a pipe instead of
storing the send on disk.  ;)



On Thu, Aug 27, 2015 at 05:59:47PM +0000, Hugo Mills wrote:
>    See my other email in this thread. :)

Didn't get that. Should I?


Kind regards for your patience and excellent code!


-- 
  E-mail is public! Talk to me in private using encryption:
         http://loupsycedyglgamf.onion/LynX/
          irc://loupsycedyglgamf.onion:67/lynX
         https://psyced.org:34443/LynX/

  reply	other threads:[~2015-08-27 18:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 17:32 Impossible to mount two different copies of the same btrfs carlo von lynX
2015-08-27 17:53 ` Chris Murphy
2015-08-27 17:59   ` Hugo Mills
2015-08-27 18:44     ` carlo von lynX [this message]
2015-08-27 18:48       ` Hugo Mills
2015-08-27 17:55 ` Hugo Mills

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=20150827184415.GA31439@lo.psyced.org \
    --to=lynx@time.to.get.psyced.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.