All of lore.kernel.org
 help / color / mirror / Atom feed
From: Milan Broz <gmazyland@gmail.com>
To: "Martin Jørgensen" <mjoerg@gmail.com>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] cryptsetup versions: cryptsetup 2.3.4 vs. cryptsetup 2.1.0 - thought I had data corruption!?!
Date: Tue, 22 Dec 2020 14:21:20 +0100	[thread overview]
Message-ID: <c20c8e02-6843-c255-76cd-61367064075f@gmail.com> (raw)
In-Reply-To: <CAJN12jmbhQfJTnCjUZKh31uQ8ZNWrsz-BKzDmLntVMd=+m2znQ@mail.gmail.com>

On 16/12/2020 01:06, Martin Jørgensen wrote:

> For the reference, if anyone experiences the same problem I don't recommend using usb at all for transferring LUKS-volumes.

Just a small addition:

This is really not LUKS specific, if you have failing HW data is going to be corrupted - just in the case of encrypted data
the error will usually propagate to whole sectors, so it is more visible to upper layer (fs).

And many external drivers or USB interfaces are really unreliable these days in long-term use...

If there is no problem with HW, LUKS can be easily used for external USB disks. In fact it is one of intended use case.

Anyway, thanks for letting us know where the problem was!

Milan
_______________________________________________
dm-crypt mailing list
dm-crypt@saout.de
https://www.saout.de/mailman/listinfo/dm-crypt

  reply	other threads:[~2020-12-22 13:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-25 17:30 [dm-crypt] cryptsetup versions: cryptsetup 2.3.4 vs. cryptsetup 2.1.0 - thought I had data corruption!?! Martin Jørgensen
2020-11-25 18:01 ` Michael Kjörling
2020-11-25 18:34   ` Milan Broz
2020-11-25 20:08     ` Martin Jørgensen
2020-11-26  9:32     ` Martin Jørgensen
2020-12-16  0:06       ` Martin Jørgensen
2020-12-16  0:06         ` Martin Jørgensen
2020-12-22 13:21         ` Milan Broz [this message]
2020-12-22 22:03           ` 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=c20c8e02-6843-c255-76cd-61367064075f@gmail.com \
    --to=gmazyland@gmail.com \
    --cc=dm-crypt@saout.de \
    --cc=mjoerg@gmail.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.