From: Zdenek Kabelac <zdenek.kabelac@gmail.com>
To: Patrick Hemmer <phemmer+lvm@stormcloud9.net>, linux-lvm@lists.linux.dev
Subject: Re: Converting thin stripe volume to linear
Date: Thu, 13 Mar 2025 19:54:54 +0100 [thread overview]
Message-ID: <c75b67e6-fff1-4a06-8abb-e0501bb039c3@gmail.com> (raw)
In-Reply-To: <0eb680b5-ad45-45e6-bc17-de052aa583a1@app.fastmail.com>
Dne 13. 03. 25 v 1:38 Patrick Hemmer napsal(a):
> I've got a LVM thin stripe volume across 2 drives that I'm trying to migrate to a new larger single drive (getting rid of the old drives). Following various information on the subject, it seems the procedure here is to first convert from stripe to mirror, and then from mirror to linear. While attempting this, I seem to have hit an issue on the second part of that process, and am not having much luck resolving it.
Hi
Likely you can convert your nearly full thin-pool with a single thin volume to
a linear LV by just taking 'dd' copy of if=/dev/thin of=/dev/linear - using
direct io option (and this can be actually faster then raid mirroring).
If you are converting _tdata - you are basically using raid1 for _tdata - but
that is no help to convert anything to linear - _tdata holds 'chunks' and how
these chunks are 'mapped' to 'create' your thinLV looking like a 'linear block
device' is fully in control by a thin-pool target and the use of _tmeta content.
While lvm2 could eventually add support doing a raid for thinLV - so you can
have your duplicate made while your device is online and in-use - currently
there is no such variant support - so you need to 'activate' thinLV
and without any use/mounting take a 'dd' copy.
>
> Any idea how I get past this point? I could just build a completely new logical volume and manually copy the data, but there's around 40 logical volumes on this thin pool, many of which are snapshots, so would be much easier to just convert it if possible.
Well once you go to thin-pool, there is no other route to go back to linear
other then 'manual copy' (and no one has even requested such feature).
Regards
Zdenek
next prev parent reply other threads:[~2025-03-13 18:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-13 0:38 Converting thin stripe volume to linear Patrick Hemmer
2025-03-13 18:54 ` Zdenek Kabelac [this message]
2025-03-13 23:14 ` Patrick Hemmer
2025-03-14 0:05 ` Zdenek Kabelac
2025-03-14 0:17 ` Patrick Hemmer
2025-03-14 0:27 ` Zdenek Kabelac
[not found] ` <a5e7c616-70d5-4108-a963-b298ce317163@app.fastmail.com>
2025-03-14 11:25 ` Zdenek Kabelac
2025-03-14 11:30 ` Patrick Hemmer
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=c75b67e6-fff1-4a06-8abb-e0501bb039c3@gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=linux-lvm@lists.linux.dev \
--cc=phemmer+lvm@stormcloud9.net \
/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).