All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] LUKS partition write-protected, mounting read-only
Date: Wed, 27 Apr 2016 02:44:38 +0200	[thread overview]
Message-ID: <20160427004438.GA32427@tansi.org> (raw)
In-Reply-To: <571FEDEE.7030904@gmail.com>

Just a guess, but maybe the second machine has limited ext4 support?
You could try with ext3 and see what happens.

Regards,
Arno

On Wed, Apr 27, 2016 at 00:38:38 CEST, Serrano Pereira wrote:
> Hello,
> 
> When I create a LUKS partition like so:
> 
> $ cryptsetup luksFormat /root/test
> $ cryptsetup open /root/test test
> $ mkfs.ext4 -j /dev/mapper/test
> $ mount /dev/mapper/test /mnt/files
> 
> Then I can create files in /mnt/files just fine. But when I copy
> /root/test to a different computer, and then do:
> 
> $ cryptsetup open /root/test test
> Enter passphrase for /root/test:
> mount: /dev/mapper/test is write-protected, mounting read-only
> $ mount /dev/mapper/test /mnt/files
> 
> As you can see, the device is mounted read-only. I cannot write any
> files to the LUKS partition. Why is this so? How can I write to the
> partition on another computer?
> 
> Regards,
> Serrano
> _______________________________________________
> dm-crypt mailing list
> dm-crypt@saout.de
> http://www.saout.de/mailman/listinfo/dm-crypt

-- 
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

  reply	other threads:[~2016-04-27  0:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 22:38 [dm-crypt] LUKS partition write-protected, mounting read-only Serrano Pereira
2016-04-27  0:44 ` Arno Wagner [this message]
2016-04-27  4:18 ` David Christensen

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=20160427004438.GA32427@tansi.org \
    --to=arno@wagner.name \
    --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 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.