linux-lvm.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
To: linux-lvm <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] Removing lvmcache fails
Date: Mon, 21 Sep 2020 12:01:22 +0200 (CEST)	[thread overview]
Message-ID: <2072153092.4261300.1600682482754.JavaMail.zimbra@karlsbakk.net> (raw)
In-Reply-To: <58ac5e5a-a3ce-6844-8a30-29f65dc857b7@redhat.com>

> Dne 21. 09. 20 v 10:51 Roy Sigurd Karlsbakk napsal(a):
>> Hi all
>> 
>> I have an ssd hooked up to my system to do some caching of the raid-6 array.
>> Now, that SSD isn't very new and has started developing some smart errors, so I
>> thought I'd just remove it and find a nice recycle bin for it. However, this
>> fails.
> 
> Hmm - cache isn't yet very easy to use once you start to have faulty devices
> in your device stack

Well, that's why I want to replace it ;)

>> This is Debian Buster (latest) with kernel 5.4 and lvm 2.03.02(2)
>> 
>> Any idea how to get rid of this?
>> 
>> # lvconvert --uncache data/data
>>    Unknown feature in status: 8 2488/262144 128 819192/819200 57263288 35277148
>>    19955332 9916661 0 1 1 3 metadata2 writethrough no_discard_passdown 2
>>    migration_threshold 2048 smq 0 rw -
> 
> 
> However since you have 'writethrough' cache mode - it should be possible to
> use  'lvconvert --uncache --force'

# lvconvert --uncache --force data/data
  Unknown feature in status: 8 2484/262144 128 819198/819200 57470386 35323243 19987362 9940326 0 0 1 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 smq 0 rw -
  Flushing 1 blocks for cache data/data.
  Unknown feature in status: 8 2484/262144 128 819198/819200 57439248 35307947 19981793 9938992 0 0 1 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 cleaner 0 rw -
  Flushing 1 blocks for cache data/data.
  Unknown feature in status: 8 2484/262144 128 819198/819200 57439248 35307947 19981793 9938992 0 0 1 3 metadata2 writethrough no_discard_passdown 2 migration_threshold 2048 cleaner 0 rw -
(et cetera et cetera ad infinitum)

> But I'm somehow confused how you can have any dirty blocks in this case ??

So am I

> lvm2 2.03.02 version was somewhat experimental release - so I've recommend
> something newer  - which will also properly parse newer status output from
> newer kernel dm-cache module.

Well, that's weird - debian is usually rather conservative on its packages in a stable release. Are you sure?

I also updated to a backported kernel 5.7 without any change.

Vennlig hilsen

roy
-- 
Roy Sigurd Karlsbakk
(+47) 98013356
http://blogg.karlsbakk.net/
GPG Public key: http://karlsbakk.net/roysigurdkarlsbakk.pubkey.txt
--
Hið góða skaltu í stein höggva, hið illa í snjó rita.

  reply	other threads:[~2020-09-21 10:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  8:51 Roy Sigurd Karlsbakk
2020-09-21  9:47 ` Zdenek Kabelac
2020-09-21 10:01   ` Roy Sigurd Karlsbakk [this message]
2020-09-21 12:53     ` Zdenek Kabelac
2020-09-21 13:24       ` Roy Sigurd Karlsbakk

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=2072153092.4261300.1600682482754.JavaMail.zimbra@karlsbakk.net \
    --to=roy@karlsbakk.net \
    --cc=linux-lvm@redhat.com \
    --subject='Re: [linux-lvm] Removing lvmcache fails' \
    /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

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).