linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Marcin Wolcendorf <antymat+redhat@chelmska.waw.pl>
Subject: Re: [linux-lvm] lvmcache writethrough synchronisation at system startup
Date: Thu, 6 Dec 2018 12:32:47 +0100	[thread overview]
Message-ID: <175fe7a5-9212-fffe-780b-5fbca0ecbcfe@redhat.com> (raw)
In-Reply-To: <20181205150113.ehnb33t7abnnrmfk@chelmska.waw.pl>

Dne 05. 12. 18 v 16:01 Marcin Wolcendorf napsal(a):
> Hi,
> 
> Thanks for your reply!
> 
> On Wed, Dec 05, 2018 at 03:23:21PM +0100, Zdenek Kabelac wrote:
>> Dne 05. 12. 18 v 7:19 Marcin Wolcendorf napsal(a):
>>> My setup:
>>> I have 2 mdraid devices: one 24T raid6, one 1T raid1, and one separate SSD. All
>>> are LUKS-encrypted, SSD is partitioned into MBR boot partition, encrypted /boot
>>> partition and a big encrypted partition for a PV. The encrypted block devices
>>> (except /boot) are PVs in my VG. The 24T RAID holds the origin LV, the 1T RAID
>>> is made into a cachepool.
>>
>> Hi
>>
>> I'd say in your case it's very important which version of kernel is in use,
>> as there very couple fixes solving this issue in not too long history.
> 
> $ uname -a
> Linux hal-9002 4.18.0-2-amd64 #1 SMP Debian 4.18.10-2 (2018-11-02) x86_64 GNU/Linux
> 
> I think it's not *that* old.
> I searched for some info about this issue, but my google mojo left me and I
> didn't find anything. Can you point me to some place - like commit or bug
> description - where I could read about those fixes?
> 
>> Secondary issue is - it's always good idea there is correct shutdown process
>> instead of just 'power-off' althouhg in 'writethrough' case it should not be
>> that big issue (but here applies the advice number one - use recent
>> kernels).
> 
> OK, so how should the shutdown look like?
> 


On i.e. Fedora distribution all filesystems are unmounted and all LVs are 
deactivatated -  due to switch to shutdown 'ramdisk' (reusing the one from 
initial boot).


Zdenek

      reply	other threads:[~2018-12-06 11:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-05  6:19 [linux-lvm] lvmcache writethrough synchronisation at system startup Marcin Wolcendorf
2018-12-05 14:23 ` Zdenek Kabelac
2018-12-05 15:01   ` Marcin Wolcendorf
2018-12-06 11:32     ` Zdenek Kabelac [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:
  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=175fe7a5-9212-fffe-780b-5fbca0ecbcfe@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=antymat+redhat@chelmska.waw.pl \
    --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).