From: Dennis Schridde <devurandom@gmx.net>
To: David Teigland <teigland@redhat.com>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] cache_check --clear-needs-check-flag does not clear needs_check flag?
Date: Wed, 09 Dec 2020 21:15:25 +0100 [thread overview]
Message-ID: <2815973.mvXUDI8C0e@monk> (raw)
In-Reply-To: <20201209193051.GC15208@redhat.com>
[-- Attachment #1.1: Type: text/plain, Size: 748 bytes --]
On Mittwoch, 9. Dezember 2020 20:30:51 CET David Teigland wrote:
> On Wed, Dec 09, 2020 at 08:06:41PM +0100, Dennis Schridde wrote:
> > How would you proceed to repair this cache? I can recreate it as a
> > cachepool, but first I need to gain back access to the data, i.e. get
> > into a state where I can --uncache.
>
> I know that cachevols do not yet work with lvconvert --repair, which uses
> cache_repair, but this must be another case where cache_repair is still
> needed. If this is writethough mode you should be able to simply drop the
> cache with lvconvert --splitcache and then recreate it.
Would this be safe if cache_dump showed all blocks are clean (dirty=false),
even if the cache was in writeback mode?
--Dennis
[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
[-- Attachment #2: Type: text/plain, Size: 197 bytes --]
_______________________________________________
linux-lvm mailing list
linux-lvm@redhat.com
https://www.redhat.com/mailman/listinfo/linux-lvm
read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
prev parent reply other threads:[~2020-12-09 20:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 21:01 [linux-lvm] cache_check --clear-needs-check-flag does not clear needs_check flag? Dennis Schridde
2020-12-08 22:19 ` Dennis Schridde
2020-12-09 11:05 ` Zdenek Kabelac
2020-12-09 19:06 ` Dennis Schridde
2020-12-09 19:30 ` David Teigland
2020-12-09 19:57 ` Dennis Schridde
2020-12-09 20:45 ` David Teigland
2020-12-09 23:52 ` David Teigland
2020-12-09 20:15 ` Dennis Schridde [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=2815973.mvXUDI8C0e@monk \
--to=devurandom@gmx.net \
--cc=linux-lvm@redhat.com \
--cc=teigland@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.