archive mirror
 help / color / mirror / Atom feed
From: Gionatan Danti <>
To: LVM general discussion and development <>
Cc: Roger Heflin <>,
	Malin Bruland <>
Subject: Re: [linux-lvm] lvconvert --uncache takes hours
Date: Thu, 02 Mar 2023 21:47:51 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Il 2023-03-02 19:33 Roger Heflin ha scritto:
> On Thu, Mar 2, 2023 at 11:44 AM Gionatan Danti <> 
> wrote:
> It is a 100G cache over 16TB, so even if it flushes in order the may
> not be that close to each other (1 in 160).

Yes, but destaging in LBA order (albeit far apart) is much better than 
in random order.

> Also if pieces are decided and added to the cached then the cache is
> not in order on the ssd and proper coalescing would require reading
> the entire cache and sorting the 3,000,000 location entries before
> starting the de-stage.  And that complication of a de-stage is likely
> not been coded yet if I was just guessing, the de-stage starts at the
> beginning and continues to the end of the cache.

I would expect reordering and coalescing to happen in reasonably sized 
window (ie: collect 64 MB of data, reorder and flush them). At the same 
time, considering how lvmcache works, you are probably right: cached 
chunks are going to be flushed as discovered (random order).

> Even coded though, if the you have enough blocks cached and if the
> blocks spread say one or 2 on each track it would break down to having
> to write a tiny bit on each track with seeks between mostly breaking
> down to the time required to simply read/write  the HD end to end.  At
> 150MB/sec (should be about the platter speed) that would take 3.5
> hours.

Which (apart being a totally worst outcome) would be way better than 
what required for totally random IO.


Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. -
email: -
GPG public key ID: FF5F32A8

linux-lvm mailing list
read the LVM HOW-TO at

      reply	other threads:[~2023-03-02 20:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-01 22:44 [linux-lvm] lvconvert --uncache takes hours Roy Sigurd Karlsbakk
2023-03-01 22:55 ` Demi Marie Obenour
2023-03-02  0:51 ` Roger Heflin
2023-03-02  8:33   ` Roy Sigurd Karlsbakk
2023-03-02 11:27     ` Roger Heflin
2023-03-02 17:34   ` Gionatan Danti
2023-03-02 18:33     ` Roger Heflin
2023-03-02 20:47       ` 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:

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