From: Dennis Schridde <devurandom@gmx.net>
To: linux-lvm@redhat.com
Cc: Dennis Schridde <devurandom@gmx.net>
Subject: Re: [linux-lvm] cache_check --clear-needs-check-flag does not clear needs_check flag?
Date: Tue, 08 Dec 2020 23:19:31 +0100 [thread overview]
Message-ID: <5447546.DvuYhMxLoT@monk> (raw)
In-Reply-To: <4384449.LvFx2qVVIh@monk>
[-- Attachment #1.1: Type: text/plain, Size: 881 bytes --]
On Sonntag, 6. Dezember 2020 22:01:37 CET Dennis Schridde wrote:
> [...]
> $ sudo lvchange -ay vg_ernie/lv_cache
> Do you want to activate component LV in read-only mode? [y/n]: y
> Allowing activation of component LV.
> [...]
> Is it possible that `cache_check --clear-needs-check-flag does not clear
> needs_check flag` does not actually clear the needs_check flag in my case?
I suspect that this has something to do with the read only status of the LV...
What if the superblock gets changed, but is then not written back to the LV,
because it is read only, and failure to write it back was not treated as an
error? I dd-ed lv_cache into a file, ran cache_check --clear-needs-check-flag
on it, and then tried to dd it back to the LV. Sadly that results in a
permission denied error. I was not able to figure out how to force writing it
back.
--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/
next prev parent reply other threads:[~2020-12-08 22:25 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 [this message]
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
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=5447546.DvuYhMxLoT@monk \
--to=devurandom@gmx.net \
--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).