From: "Ivan Labáth" <ilabath@gmail.com>
To: Hugo Mills <hugo-lkml@carfax.org.uk>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: raw fs backup/copy
Date: Thu, 06 Jan 2011 20:26:10 +0100 [thread overview]
Message-ID: <4D261752.9030800@gmail.com> (raw)
In-Reply-To: <20110106183507.GA19633@carfax.org.uk>
On 01/06/11 19:35, Hugo Mills wrote:
> On Thu, Jan 06, 2011 at 05:36:48PM +0100, Ivan Lab=C3=A1th wrote:
>> Is there a reason one can not mount a btrfs and it's byte-for-byte
>> copy in parallel, or is the driver just acting silly?
>=20
> Probably because both filesystems have identical UUIDs (and labels=
)
> and so will (I suspect) end up being identified as the same filesyste=
m
> by the btrfs code.
>=20
> Hugo.
>=20
The reason I ask is, that I had a mirror RAID (btrfs on LVM on LUKS on =
RAID)
across 2 disks. Then I snatched one to take with me when going away for
holidays, copied some files on to it and when I came back, I wanted to =
get
to those files. The problem was, I couldn't mount the fs I took with me=
,
because a similar fs was already mounted. As it wasn't the root fs,
I could unmount it and copy the files on some other fs
(though one could use pivot_root, if it was the root fs).
It seems to me there are cases, where one would want to mount two copie=
s of
originally the same filesystem - think of RAID, VMs, distributing fs im=
ages
on a network, LVM snapshots, backups, etc.
--
ivan
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" =
in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-01-06 19:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 16:36 raw fs backup/copy Ivan Labáth
[not found] ` <20110106183507.GA19633@carfax.org.uk>
2011-01-06 19:26 ` Ivan Labáth [this message]
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=4D261752.9030800@gmail.com \
--to=ilabath@gmail.com \
--cc=hugo-lkml@carfax.org.uk \
--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.