From: Ritesh Raj Sarraf <rrs@researchut.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] dm-crypt LUKS and USB power management
Date: Mon, 30 May 2016 22:14:08 +0530 [thread overview]
Message-ID: <1464626648.3187.12.camel@researchut.com> (raw)
In-Reply-To: <573FB404.4000405@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1279 bytes --]
On Sat, 2016-05-21 at 03:04 +0200, Axel Heider wrote:
>
> I wonder if there are any ideas how dm-crypto or LUKS can handle this
> case. Or is the recommendation that the USB suspend should not happen
> at all for devices that are broken (ie. that disconnect and reconnect
> on resume)?
> Even if all handles on /dev/sda are released internally, there is not
> really a guarantee that the devices comes back as /dev/sda are the
> disconnect/reconnect. However, the UUID should be the same, so that
> could be used to detect it's the same device and partition then and
> accesses get re-routed to it then transparently.
I doubt if it could be done clean. Most targets in Device Mapper ask for careful
unstacking.
Red Hat (leading Linux vendor) still seems to be recommending that.
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html-si
ngle/Storage_Administration_Guide/#removing_devices
I would rather investigate the (flaky) USB device. First, does it happen only
when Runtime PM is enabled ? If so, you should just blacklist it from Power
Management. Many devices, under Linux, report (false) PM capabilities.
--
Given the large number of mailing lists I follow, I request you to CC
me in replies for quicker response
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2016-05-31 6:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-21 1:04 [dm-crypt] dm-crypt LUKS and USB power management Axel Heider
2016-05-30 16:44 ` Ritesh Raj Sarraf [this message]
2016-05-31 10:59 ` Axel Heider
2016-05-31 18:19 ` Arno Wagner
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=1464626648.3187.12.camel@researchut.com \
--to=rrs@researchut.com \
--cc=dm-crypt@saout.de \
/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