archive mirror
 help / color / mirror / Atom feed
From: Mike Snitzer <>
To: Michael Lipp <>
Cc: LVM general discussion and development <>
Subject: Re: [linux-lvm] Deeply impressed
Date: Wed, 22 Jan 2020 11:01:43 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, Jan 22 2020 at 10:40am -0500,
Michael Lipp <> wrote:

> Just for once, I wanted to state that I am deeply impressed by the work
> done with LVM. I have just just copied all my data from my old RAID to
> my new RAID while continuing to work with the data using pvmove.
> Compared with what I had to do several years ago, this was a great
> experience. I know, of course, that professional operators do this "all
> day", but doing it yourself for once felt great.
> Just one question, though. I couldn't find anything about using pvmove
> together with lvm cache. So to make sure, I removed the SSD caching
> before pvmove and added the caching again afterwards. Would it have been
> safe to leave the caching active during the pvmove?

No, fairly certain pvmove wouldn't have allowed the caching layer.  So
you did the correct sequence.

      reply	other threads:[~2020-01-22 16:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 15:40 [linux-lvm] Deeply impressed Michael Lipp
2020-01-22 16:01 ` Mike Snitzer [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).