From: Ryan Launchbury <ryan@magenta.tv>
To: Gionatan Danti <g.danti@assyoma.it>
Cc: 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: Fri, 22 Jun 2018 20:22:10 +0100 [thread overview]
Message-ID: <CAG+RErkXvs2Qr08C4h_uHuv__dknkoF80iwTVuHqJ_zCzBo=uA@mail.gmail.com> (raw)
In-Reply-To: <39a2408c600ed4caf00724eb72c191c2@assyoma.it>
[-- Attachment #1: Type: text/plain, Size: 804 bytes --]
Hi Gionatan,
My development system is out on rental at the moment. I'll check that for
you as soon as I can.
Best regards,
Ryan
On Fri, Jun 22, 2018 at 7:13 PM, Gionatan Danti <g.danti@assyoma.it> wrote:
> 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?
>
> --
> Danti Gionatan
> Supporto Tecnico
> Assyoma S.r.l. - www.assyoma.it
> email: g.danti@assyoma.it - info@assyoma.it
> GPG public key ID: FF5F32A8
>
--
*Ryan Launchbury*
System Engineer
magenta broadcast
magenta.tv
mob: 07939 276 897
support: 020 8050 1920
office: 020 8050 1080
[-- Attachment #2: Type: text/html, Size: 2769 bytes --]
next prev parent reply other threads:[~2018-06-22 19:22 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 [this message]
2018-06-22 20:07 ` Zdenek Kabelac
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='CAG+RErkXvs2Qr08C4h_uHuv__dknkoF80iwTVuHqJ_zCzBo=uA@mail.gmail.com' \
--to=ryan@magenta.tv \
--cc=g.danti@assyoma.it \
--cc=linux-lvm@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 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).