From: Hans van Kranenburg <hans.van.kranenburg@mendix.com>
To: Duncan <1i5t5.duncan@cox.net>, linux-btrfs@vger.kernel.org
Subject: Re: Experiences with metadata balance/convert
Date: Sat, 22 Apr 2017 23:18:42 +0200 [thread overview]
Message-ID: <2866c3e6-2be9-897b-386a-a3cc1d0ca43a@mendix.com> (raw)
In-Reply-To: <pan$4a44a$5b70b88a$e087c574$18e5ec69@cox.net>
On 04/22/2017 11:17 AM, Duncan wrote:
> Hans van Kranenburg posted on Fri, 21 Apr 2017 12:26:18 +0200 as
> excerpted:
>
>> So, I used the clone functionality of the underlying iSCSI target to get
>> a writable throw-away version of the filesystem to experiment with
>> (great!).
>
> Please, I'm rather sure you know all this and have setup your system
> accordingly, but we need to try to make it explicit any time there's
> mention of any sort of device or filesystem cloning tool, that we tell
> others that may happen on the post either just reading the list or via a
> google or the like...
Ack. [1]
[1]
https://btrfs.wiki.kernel.org/index.php/Gotchas#Block-level_copies_of_devices
> [..... .. .. . ... .. . . .. . ..]
> (Of course the above is an explanation in far more detail than that
> single-liner, because it's the full topic of the post and I might as
> well, compared to the simple parenthetical I'm asking for when clone
> discussions come up.)
Thanks for stressing the fact.
And yes, the cloned iSCSI luns are only visible to a completely separate
server configured in another initiator group of the target, seen by
hardware that is not aware of what's happenning in the production cluster.
--
Hans van Kranenburg
next prev parent reply other threads:[~2017-04-22 21:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 10:26 Experiences with metadata balance/convert Hans van Kranenburg
2017-04-21 10:31 ` Hans van Kranenburg
2017-04-21 11:13 ` Hans van Kranenburg
2017-04-21 11:27 ` Austin S. Hemmelgarn
2017-04-22 9:17 ` Duncan
2017-04-22 21:18 ` Hans van Kranenburg [this message]
2017-04-22 16:45 ` Chris Murphy
2017-04-22 16:55 ` Chris Murphy
2017-04-22 20:22 ` Hans van Kranenburg
2017-04-22 20:33 ` Hans van Kranenburg
2017-04-22 20:21 ` Hans van Kranenburg
2017-04-23 9:45 ` Hans van Kranenburg
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=2866c3e6-2be9-897b-386a-a3cc1d0ca43a@mendix.com \
--to=hans.van.kranenburg@mendix.com \
--cc=1i5t5.duncan@cox.net \
--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).