From: Gionatan Danti <g.danti@assyoma.it>
To: Zdenek Kabelac <zkabelac@redhat.com>
Cc: Launchbury <ryan@magenta.tv>,
Ryan,
LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Unable to un-cache logical volume when chunk size is over 1MiB
Date: Sat, 23 Jun 2018 12:09:21 +0200 [thread overview]
Message-ID: <c351a57bdcf219c04b315aa02b6207ea@assyoma.it> (raw)
In-Reply-To: <326c998e-67f8-6331-c8f1-a22e8c06fd98@redhat.com>
Il 22-06-2018 22:07 Zdenek Kabelac ha scritto:
> When cache will experience write error - it will become invalidate and
> will
> need to be dropped - but this thing is not automated ATM - so admin
> works is needed to handle this task.
So, if a writethrough cache experience write errors but the
administrator is not able to immediately intervene to drop the cache,
what problem can arise? Stale reads? Slow performance?
What about cache *read* error? Is the read simply redirected to the
underlying slow/main volume?
Thanks.
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. - www.assyoma.it
email: g.danti@assyoma.it - info@assyoma.it
GPG public key ID: FF5F32A8
next prev parent reply other threads:[~2018-06-23 10:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 9:18 [linux-lvm] Unable to un-cache logical volume when chunk size is over 1MiB Ryan Launchbury
2018-06-20 10:15 ` Zdenek Kabelac
2018-06-20 11:10 ` Ryan Launchbury
2018-06-22 18:13 ` Gionatan Danti
2018-06-22 19:22 ` Ryan Launchbury
2018-06-22 20:07 ` Zdenek Kabelac
2018-06-23 10:09 ` Gionatan Danti [this message]
2018-06-24 19:18 ` Ryan Launchbury
2018-06-25 17:19 ` Gionatan Danti
2018-06-25 17:20 ` Ryan Launchbury
2018-06-25 17:40 ` Gionatan Danti
2018-07-18 14:25 ` Ryan Launchbury
2018-07-18 14:58 ` Douglas Paul
2019-01-21 20:19 ` 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=c351a57bdcf219c04b315aa02b6207ea@assyoma.it \
--to=g.danti@assyoma.it \
--cc=linux-lvm@redhat.com \
--cc=ryan@magenta.tv \
--cc=zkabelac@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.