All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nils Radtke <Nils.Radtke@Think-Future.de>
To: Milan Broz <mbroz@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cryptsetup + lvm on usb disk, unusable /dev/dm-* after suspend/resume   cycle
Date: Mon, 26 Jul 2010 17:56:27 +0200	[thread overview]
Message-ID: <20100726155627.GN31966@localhost> (raw)
In-Reply-To: <4C4D8C25.8040704@redhat.com>

  Hi Milan,

  Thank you for your explanation.

  So I'll try to find logs regarding this issue (won't be easy though..).

  On the other hand, the usb device survives suspend/resume normally, that is,
  when using a plain disk, std partition etc.

  Ok, I'm going for the logs and if found be back.

  Thank you again for your help.


                  Nils



On Mon 2010-07-26 @ 03-22-45PM +0200, Milan Broz wrote: 
# On 07/26/2010 03:06 PM, Nils Radtke wrote:
# > That's what I tried and failed gloriously. I'm trying to revive my memory about the 
# > situation: fs could be unmounted, however, the cryptsetup luksClose failed (IRC) and 
# > therefore the dmsetup remove consequently failed also.
# 
# So instead of "cryptsetup luksClose" use dmsetup remove for crypt device too
# (There was a bug in some version of cryptsetup which failed close if underlying device
# disappeared, should be fixed in >=1.1.2, anyway "dmsetup remove" is low-level equivalent.)
# 
# Also see man page and "dmsetup remove -f" flag.
# 
# The usb device reinitialization is separate problem, maybe someone can help if you provide
# more logs.
# 
# Milan


      reply	other threads:[~2010-07-26 15:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-25 16:06 cryptsetup + lvm on usb disk, unusable /dev/dm-* after suspend/resume cycle Nils Radtke
2010-07-25 21:00 ` Milan Broz
2010-07-26 13:06   ` Nils Radtke
2010-07-26 13:22     ` Milan Broz
2010-07-26 15:56       ` Nils Radtke [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=20100726155627.GN31966@localhost \
    --to=nils.radtke@think-future.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbroz@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.