All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>,
	Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Subject: Re: [linux-lvm] Removing lvmcache fails
Date: Mon, 21 Sep 2020 11:47:05 +0200	[thread overview]
Message-ID: <58ac5e5a-a3ce-6844-8a30-29f65dc857b7@redhat.com> (raw)
In-Reply-To: <552451034.4238344.1600678309529.JavaMail.zimbra@karlsbakk.net>

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

> 
> 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'

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

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.

Regards

Zdenek

  reply	other threads:[~2020-09-21  9:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21  8:51 [linux-lvm] Removing lvmcache fails Roy Sigurd Karlsbakk
2020-09-21  9:47 ` Zdenek Kabelac [this message]
2020-09-21 10:01   ` Roy Sigurd Karlsbakk
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=58ac5e5a-a3ce-6844-8a30-29f65dc857b7@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=linux-lvm@redhat.com \
    --cc=roy@karlsbakk.net \
    /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.