From: "Michael Niederle" <mniederle@gmx.at>
To: linux-btrfs@vger.kernel.org
Subject: btrfs-images
Date: Wed, 4 Aug 2010 18:13:32 +0200 [thread overview]
Message-ID: <20100804181332.1c5ea14a@simplux> (raw)
Hi!
I also wanted to use btrfs-images, but changed my mind when I got troubles
with several btrfs file systems derived from the same image.
If more than one of these file system were physically connected at the same
time, mounting one of them resulted in a mess. I think they all used the same
internal ids and btrfs thought them to be one single file system stretched over
several media. So I decided to create a fresh btrfs file system every time and
copy the files from an archive (which is much slower).
Is there a workaround?
Greetings, Michael
reply other threads:[~2010-08-04 16:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100804181332.1c5ea14a@simplux \
--to=mniederle@gmx.at \
--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).