From: Gionatan Danti <g.danti@assyoma.it>
To: LVM general discussion and development <linux-lvm@redhat.com>
Cc: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Subject: Re: [linux-lvm] LVM and HSM?
Date: Mon, 13 May 2019 19:24:50 +0200 [thread overview]
Message-ID: <5343bab31e1d4ec5162cd73342388596@assyoma.it> (raw)
In-Reply-To: <7e07a7b4-c4c3-bb43-6305-3949c1d1a849@redhat.com>
Il 13-05-2019 10:26 Zdenek Kabelac ha scritto:
> Hi
>
> There is no technical problem to enable caching of cached volume (aka
> convert cache_cdata LV into another 'cached' volume.
> And as long as there are not errors anywhere - it works.
> Difficulty comes with solving error cases - and that's the main reason
> it's not enable so far.
> So I don't see big issue with enabling usage on 'user's own risk'.
Hi, how "cache of cached volume" is tiered/hierarchical storage?
In such a case, total available space is the sum of all storage
hierarchy. For example, using 1 TB SSD + 8 TB HDD would result in 9 TB
total in a tiered/hierarchical case, while "only" 8 TB on a cached
setup.
Am I missing something here?
The interesting thing is that LVM already supports something similar to
tiered storage, as pvmove can be used to migrate hot physical extent to
faster devices. The hard/manual thing is to determine *which* extent to
move/migrate.
Regards.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
prev parent reply other threads:[~2019-05-13 17:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-11 22:07 [linux-lvm] LVM and HSM? Roy Sigurd Karlsbakk
2019-05-13 8:26 ` Zdenek Kabelac
2019-05-13 17:24 ` Gionatan Danti [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:
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=5343bab31e1d4ec5162cd73342388596@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-lvm@redhat.com \
--cc=roy@karlsbakk.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).