From: Arno Wagner <arno@wagner.name>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] Avoiding fsck.ext4 destruction of crypto_luks data
Date: Sun, 30 Dec 2012 14:19:39 +0100 [thread overview]
Message-ID: <20121230131938.GA15212@tansi.org> (raw)
In-Reply-To: <50E032CA.1010004@gmail.com>
On Sun, Dec 30, 2012 at 01:25:46PM +0100, Milan Broz wrote:
> On 12/30/2012 01:08 PM, Sven Eschenberg wrote:
> >> I also found that "wipefs"
> >> does not remove matadata 0.90 signatures from md components (located
> >> at the end. I still use them because I like kernel-level autodetection
> >> and my arrays are small), also added warning about that.
>
> Usual util-linux maintainer response is "send a patch" :-)
>
> wipefs must work (e.g. anaconda installer depends on the proper sig. erase)
> so it is a bug somewhere.
>
> Do you have reproducer? (only 0.9 metadata end-of-disk format?)
Reproduce with (adjust loop2 and md12 numbers as needed):
------
head -c 1M /dev/zero > t
losetup /dev/loop2 t
mdadm --create --metadata=0.90 --force -l 1 -n 1 /dev/md12 /dev/loop2
mdadm --stop /dev/md12
mdadm --examine /dev/loop2
--> Raid componend with intact magic
wipefs /dev/loop2
mdadm --examine /dev/loop2
--> same as above, RAID signature still there
------
Version (Debian stable): util-linux: 2.17.2-9
Arno
--
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
----
One of the painful things about our time is that those who feel certainty
are stupid, and those with any imagination and understanding are filled
with doubt and indecision. -- Bertrand Russell
next prev parent reply other threads:[~2012-12-30 13:19 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 [this message]
2012-12-30 16:59 ` Emily Williams
2012-12-30 18:49 ` Matthias Schniedermeyer
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=20121230131938.GA15212@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox