From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
Gionatan Danti <g.danti@assyoma.it>
Cc: Ryan Launchbury <ryan@magenta.tv>
Subject: Re: [linux-lvm] Unable to un-cache logical volume when chunk size is over 1MiB
Date: Fri, 22 Jun 2018 22:07:11 +0200 [thread overview]
Message-ID: <326c998e-67f8-6331-c8f1-a22e8c06fd98@redhat.com> (raw)
In-Reply-To: <39a2408c600ed4caf00724eb72c191c2@assyoma.it>
Dne 22.6.2018 v 20:13 Gionatan Danti napsal(a):
> Il 20-06-2018 12:15 Zdenek Kabelac ha scritto:
>> Hi
>>
>> Aren't there any kernel write errors in your 'dmegs'.
>> LV becomes fragile if the associated devices with cache are having HW
>> issues (disk read/write errors)
>>
>> Zdenek
>
> Is that true even when using a writethrough cache mode?
With writethrough - all writes are first committed on 'origin' disk - before
they are ack back to writing apps - so cache can be through away anytime.
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.
Regards
Zdenek
next prev parent reply other threads:[~2018-06-22 20:07 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 [this message]
2018-06-23 10:09 ` Gionatan Danti
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=326c998e-67f8-6331-c8f1-a22e8c06fd98@redhat.com \
--to=zkabelac@redhat.com \
--cc=g.danti@assyoma.it \
--cc=linux-lvm@redhat.com \
--cc=ryan@magenta.tv \
/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).