From: Kai Krakow <hurikhan77@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: bad metadata crossing stripe boundary
Date: Sat, 2 Apr 2016 20:31:17 +0200 [thread overview]
Message-ID: <20160402203117.4d815f13@jupiter.sol.kaishome.de> (raw)
In-Reply-To: 20160402094432.GQ9342@torres.zugschlus.de
Am Sat, 2 Apr 2016 11:44:32 +0200
schrieb Marc Haber <mh+linux-btrfs@zugschlus.de>:
> On Sat, Apr 02, 2016 at 11:03:53AM +0200, Kai Krakow wrote:
> > Am Fri, 1 Apr 2016 07:57:25 +0200
> > schrieb Marc Haber <mh+linux-btrfs@zugschlus.de>:
> > > On Thu, Mar 31, 2016 at 11:16:30PM +0200, Kai Krakow wrote:
> [...]
> [...]
> [...]
> > >
> > > I cryptsetup luksFormat'ted the partition before I mkfs.btrfs'ed
> > > it. That should do a much better job than wipefsing it, shouldnt
> > > it?
> >
> > Not sure how luksFormat works. If it encrypts what is already on the
> > device, it would also encrypt orphan superblocks.
>
> It overwrites the LUKS metadata including the symmetric key that was
> used to encrypt the existing data. Short of Shor's Algorithm and
> Quantum Computers, after that operation it is no longer possible to
> even guess what was on the disk before.
If it was encrypted before... ;-)
--
Regards,
Kai
Replies to list-only preferred.
next prev parent reply other threads:[~2016-04-02 18:31 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-22 8:03 csum errors in VirtualBox VDI files Kai Krakow
2016-03-22 8:06 ` Kai Krakow
2016-03-22 8:07 ` Kai Krakow
2016-03-22 8:47 ` Qu Wenruo
2016-03-22 18:48 ` Kai Krakow
2016-03-22 19:42 ` Chris Murphy
2016-03-22 20:35 ` Kai Krakow
2016-03-23 4:16 ` Qu Wenruo
2016-03-26 19:30 ` Kai Krakow
2016-03-26 20:28 ` Chris Murphy
2016-03-26 21:04 ` Chris Murphy
2016-03-27 1:30 ` Kai Krakow
2016-03-27 4:57 ` Chris Murphy
2016-03-27 17:31 ` Kai Krakow
2016-03-27 19:04 ` Chris Murphy
2016-03-28 10:30 ` Kai Krakow
2016-03-27 1:01 ` Kai Krakow
2016-03-27 1:50 ` Kai Krakow
2016-03-27 4:43 ` Chris Murphy
2016-03-27 13:55 ` Qu Wenruo
2016-03-28 10:02 ` bad metadata crossing stripe boundary (was: csum errors in VirtualBox VDI files) Kai Krakow
2016-03-31 1:33 ` bad metadata crossing stripe boundary Qu Wenruo
2016-03-31 2:31 ` Qu Wenruo
2016-03-31 20:27 ` Kai Krakow
2016-03-31 20:37 ` Henk Slager
2016-03-31 21:00 ` Marc Haber
2016-03-31 21:16 ` Kai Krakow
2016-03-31 21:35 ` Kai Krakow
2016-04-01 5:57 ` Marc Haber
2016-04-02 9:03 ` Kai Krakow
2016-04-02 9:44 ` Marc Haber
2016-04-02 18:31 ` Kai Krakow [this message]
2016-04-02 19:39 ` Patrik Lundquist
2016-04-03 8:39 ` Marc Haber
2016-04-02 19:41 ` Chris Murphy
2016-04-03 8:51 ` Marc Haber
2016-04-03 18:29 ` Chris Murphy
2016-03-27 13:46 ` csum errors in VirtualBox VDI files Qu Wenruo
2016-03-22 20:07 ` Henk Slager
2016-03-22 21:23 ` Kai Krakow
2016-03-27 12:18 ` Martin Steigerwald
2016-03-27 16:53 ` Kai Krakow
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=20160402203117.4d815f13@jupiter.sol.kaishome.de \
--to=hurikhan77@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).