From: Arno Wagner <wagner@arnowagner.info>
To: Fernando <s.frmattos@gmail.com>
Cc: cryptsetup@lists.linux.dev
Subject: Re: [Question] Luks container mounted on multiple devices via network
Date: Thu, 29 Jun 2023 15:18:02 +0200 [thread overview]
Message-ID: <20230629131802.GA2765@tansi.org> (raw)
In-Reply-To: <CAF8rEhp6KN18ZAMCs-vt1dfXt3CJyN3pQbxyKu7w2EUrSt0yQA@mail.gmail.com>
Hi Fernando,
you very likelt do not have a LUKS problem. As long as you
can see anything in the LUKS container, LUKS is doing its job.
What I think may be the problem here is some file-system
incompatibility, like extended attributes on Debian or the
like. You may want to look at the mount-option each system uses.
I cannot really help you more, I have never run into this
type of problem.
Arno
On Wed, Jun 28, 2023 at 23:27:20 CEST, Fernando wrote:
> I have a 50GB container stored on a NAS I've been using for more than
> a year. Today, I needed to mount this container on multiple devices
> (Debian, Kali and WSL), and I had no problems, until I noticed that
> the files transferred from DEBIAN to the container were not displayed
> on KALI and WSL. I unmounted the container on all devices and
> remounted. The files are there, but I can only see it on the device
> that saved the files. All devices are using the same version of
> cryptsetup.
>
> Is that normal? Am I missing something?
> I'm backing up all the files, and I noticed no damage to the files.
--
Arno Wagner, Dr. sc. techn., Dipl. Inform., Email: arno@wagner.name
GnuPG: ID: CB5D9718 FP: 12D6 C03B 1B30 33BB 13CF B774 E35C 5FA1 CB5D 9718
----
A good decision is based on knowledge and not on numbers. -- Plato
If it's in the news, don't worry about it. The very definition of
"news" is "something that hardly ever happens." -- Bruce Schneier
prev parent reply other threads:[~2023-06-29 13:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 21:27 [Question] Luks container mounted on multiple devices via network Fernando
2023-06-29 13:18 ` Arno Wagner [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=20230629131802.GA2765@tansi.org \
--to=wagner@arnowagner.info \
--cc=arno@wagner.name \
--cc=cryptsetup@lists.linux.dev \
--cc=s.frmattos@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox