From: Ondrej Kozina <okozina@redhat.com>
To: peljasz@yahoo.co.uk
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] LVM cache/dm-cache questions.
Date: Mon, 29 Aug 2016 17:08:17 +0200 [thread overview]
Message-ID: <8904dd7f-5efa-6337-aafc-8b7fe2a08842@redhat.com> (raw)
In-Reply-To: <62f29dda-8a04-9125-8b3e-3e9925f485e3@yahoo.co.uk>
Thank you for the lsblk and lvs output. At least now we know that raid
is somehow involved in the setup...
On 08/29/2016 04:22 PM, lejeczek wrote:
> I cannot debug now as for now I've given up the idea to
> encrypt this LV, but I would say is should be easily
> reproducible (maybe even waste of time looking at my setup)
> I simply tried:
Well, without the debug output from cryptsetup I can't be of any more
help, I'm sorry. It's like starring into crystal ball guessing what may
have gone wrong. The -22 error code is general "wrong parameters"
answer. I don't even know if cryptsetup has got into code path where
it's supposed to open the device for write.
But let me give it one last shot. Did you by any chance end up with 22
right after the prompt:
"Are you sure? (Type uppercase yes):"
If so, are you sure that your answer was 'YES' instead of lowercase 'yes'?
Regards
Ondrej
next prev parent reply other threads:[~2016-08-29 15:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 0:36 [linux-lvm] LVM cache/dm-cache questions sergei
2016-06-20 16:27 ` Brassow Jonathan
2016-06-20 21:34 ` Sergei Franco
2016-08-25 11:51 ` lejeczek
2016-08-25 14:47 ` Xen
2016-08-26 12:45 ` lejeczek
2016-08-26 13:28 ` Xen
2016-08-26 14:01 ` lejeczek
2016-08-26 14:45 ` Ondrej Kozina
2016-08-29 9:42 ` lejeczek
2016-08-29 11:22 ` Ondrej Kozina
2016-08-29 14:22 ` lejeczek
2016-08-29 15:08 ` Ondrej Kozina [this message]
2016-08-30 8:39 ` lejeczek
2016-08-29 16:07 ` Xen
2016-08-26 17:55 ` Xen
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=8904dd7f-5efa-6337-aafc-8b7fe2a08842@redhat.com \
--to=okozina@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=peljasz@yahoo.co.uk \
/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).