DM-Crypt Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Karl O. Pinc" <kop@meme.com>
To: dm-crypt@saout.de
Subject: Re: [dm-crypt] openLuks failing - semaphore weird bug involved ?
Date: Thu, 08 Sep 2011 17:21:35 -0500	[thread overview]
Message-ID: <1315520495.15393.0@mofo> (raw)
In-Reply-To: <CAMw1ynTReMNcx=rqg-QPUhVhBh3DJLZ4biONNZay8JL2DQotVA@mail.gmail.com> (from flyingstar16@gmail.com on Thu Sep  8 16:53:45 2011)

On 09/08/2011 04:53:45 PM, Claudio Moretti wrote:
> well, you were lucky you lost only unimportant data :) there were a
> lot of people, first of all: me, who did not backup their header on
> the main system.. And they (read: me) lost access to their home
> partition because the only place where the passphrase had been stored
> was.. the damaged root partition..
> And that's how i learned i should back up headers (lol)

As I'm sure has been said by others: it's a lot more important
to back up your _data_ than to backup the luks header.

To paraphrase R. Crumb: "It is better to have data
in times of no luks header than it is to have a luks header
in times of no data."


Karl <kop@meme.com>
Free Software:  "You don't pay back, you pay forward."
                 -- Robert A. Heinlein

  reply	other threads:[~2011-09-08 22:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-07 18:30 [dm-crypt] openLuks failing - semaphore weird bug involved ? Ric Flomag
2011-09-07 22:31 ` Arno Wagner
2011-09-08 15:46 ` Ric Flomag
2011-09-08 18:11   ` Arno Wagner
2011-09-08 21:53     ` Claudio Moretti
2011-09-08 22:21       ` Karl O. Pinc [this message]
2011-09-09 16:19         ` Arno Wagner
     [not found]   ` <1315506605.6590.0@mofo>
2011-09-15 15:54     ` Ric Flomag
2011-09-15 16:06       ` Arno Wagner
2011-09-15 16:15         ` Ricflomag
2011-09-15 23:07           ` Arno Wagner

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=1315520495.15393.0@mofo \
    --to=kop@meme.com \
    --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