From: Alexander Pashaliyski <al.pashaliyski@gmail.com>
To: Zdenek Kabelac <zkabelac@redhat.com>, dm-devel@redhat.com
Subject: Re: dm-cache issue
Date: Mon, 14 Nov 2016 18:05:18 +0200 [thread overview]
Message-ID: <dbe1951c-8fd8-2e73-53ec-ec70d4e0efa6@gmail.com> (raw)
In-Reply-To: <884adfe3-ac18-5e37-f4b4-478e5031f35f@redhat.com>
On 11/14/2016 05:34 PM, Zdenek Kabelac wrote:
> Dne 14.11.2016 v 16:02 Alexander Pashaliyski napsal(a):
>> Hi guys,
>>
>>
>> I am in a process of evaluating dm-cache for our backup system.
>>
>> Currently I have an issue when restart the backup server. The server is
>> booting for hours, because of IO load. It seems is triggered a flush
>> from SSD
>> disk (that is used for a cache device) to the raid controllers (they
>> are with
>> slow SATA disks).
>> I have 10 cached logical volumes in *writethrough mode*, each with 2T
>> of data
>> over 2 raid controllers. I use a single SSD disk for the cache.
>> The backup system is with lvm2-2.02.164-1 & kernel 4.4.30.
>>
>>
>> Do you have any ideas why such flush is triggered? In writethrough
>> cache mode
>> we shouldn't have dirty blocks in the cache.
>>
>
> Hi
>
> Have you ensured there was proper shutdown ?
> Cache needs to be properly deactivated - if it's just turned off,
> all metadata are marked dirty.
>
>
> Regards
>
> Zdenek
>
Hi Zdenek,
Thank you for your answer.
Yes, I am sure. I have modified the lvm2 init script to de-activate all
logical volumes and then volume groups, but the issue still persist.
Regards,
Alex
next prev parent reply other threads:[~2016-11-14 16:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 15:02 dm-cache issue Alexander Pashaliyski
2016-11-14 15:34 ` Zdenek Kabelac
2016-11-14 16:05 ` Alexander Pashaliyski [this message]
2016-11-15 12:38 ` Teodor Milkov
2016-11-16 9:24 ` Zdenek Kabelac
2016-11-16 13:45 ` Teodor Milkov
2016-11-16 14:06 ` Zdenek Kabelac
2016-11-19 17:07 ` Teodor Milkov
2016-12-02 19:49 ` Teodor Milkov
2016-11-15 19:57 ` John Stoffel
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=dbe1951c-8fd8-2e73-53ec-ec70d4e0efa6@gmail.com \
--to=al.pashaliyski@gmail.com \
--cc=dm-devel@redhat.com \
--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.