From: Matthias Schniedermeyer <ms@citd.de>
To: Emily Williams <emilyw@MIT.EDU>
Cc: dm-crypt@saout.de
Subject: Re: [dm-crypt] Avoiding fsck.ext4 destruction of crypto_luks data
Date: Sun, 30 Dec 2012 19:49:43 +0100 [thread overview]
Message-ID: <20121230184943.GA18824@citd.de> (raw)
In-Reply-To: <CA+VYMuZT3wnwA4nJd=WjgugwpvoV8n+zKKYEE+H02HY1CB=sjQ@mail.gmail.com>
On 30.12.2012 11:59, Emily Williams wrote:
>
> So I've taken to setting my encrypted partitions to "NetBSD Encrypted"
> (a905), so when I look at the partition tables I'm reminded that there
> actually isn't a Linux filesystem on the device itself, but rather
> something that is encrypted that becomes a Linux filesystem via
> /dev/mapper/X after cryptosetup luksOpen happens.
I create a dummy partition with type 'da' (Non-FS-Data) on my HDDs.
Altough 0 (Empty) sounds nice too. ;-)
I say dummy partition because i don't actually use the partition for
anything. It's only there to stop my encryption init-script, so that i
don't accidentally kill an already initialized HDD (or one of the
system-HDDs) in case i fat-fingered the device-name.
--
Matthias
next prev parent reply other threads:[~2012-12-30 18:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-27 6:12 [dm-crypt] Avoiding fsck.ext4 destruction of crypto_luks data Emily Williams
2012-12-27 9:35 ` ken
2012-12-27 9:52 ` Arno Wagner
2012-12-28 14:46 ` Sven Eschenberg
2012-12-28 15:04 ` Arno Wagner
2012-12-28 19:22 ` Milan Broz
2012-12-29 7:06 ` Arno Wagner
2012-12-29 9:05 ` Milan Broz
2012-12-29 11:52 ` Arno Wagner
2012-12-30 8:42 ` Sven Eschenberg
2012-12-30 9:39 ` Milan Broz
2012-12-30 10:53 ` Arno Wagner
2012-12-30 12:08 ` Sven Eschenberg
2012-12-30 12:25 ` Milan Broz
2012-12-30 13:19 ` Arno Wagner
2012-12-30 16:59 ` Emily Williams
2012-12-30 18:49 ` Matthias Schniedermeyer [this message]
2012-12-30 19:45 ` Arno Wagner
2012-12-31 6:37 ` Sven Eschenberg
2012-12-31 12:40 ` Richard
2012-12-27 20:29 ` Richard
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=20121230184943.GA18824@citd.de \
--to=ms@citd.de \
--cc=dm-crypt@saout.de \
--cc=emilyw@MIT.EDU \
/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