linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Oliver Rath <rath@mglug.de>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: [linux-lvm] mixed ssd/disk szenario question: moving lv from ssd ->disk?
Date: Tue, 18 Nov 2014 17:28:05 +0100	[thread overview]
Message-ID: <546B7395.3020305@mglug.de> (raw)

Hi list,

I have an vg over multiple disks (ssd and standard disks) and a big
thinpool-volume inside. From thin thinpool i create a lot of snaps
(>200), which are normally explizit placed on the ssd (i can select the
pv-path on lvcreate).

Now, after a time some of these snaps i dont need on the fast device and
want to mv them to a slow pv (standard disk) as a kind of backup.

Ist it possible to "move" a lv from the ssd to a disk, if both devices
are part of my vg?

Tfh!
Oliver

             reply	other threads:[~2014-11-18 16:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 16:28 Oliver Rath [this message]
2014-11-18 16:55 ` [linux-lvm] mixed ssd/disk szenario question: moving lv from ssd ->disk? matthew patton
2014-11-23 11:42   ` Oliver Rath
2014-11-23 11:47   ` Oliver Rath
2014-11-27  9:27     ` Zdenek Kabelac

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=546B7395.3020305@mglug.de \
    --to=rath@mglug.de \
    --cc=linux-lvm@redhat.com \
    /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).