All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David Christensen" <dpchrist@holgerdanske.com>
To: dm-crypt@saout.de
Cc: spamzad@googlemail.com
Subject: Re: [dm-crypt] Broken header of a luks-partition - more than once
Date: Mon, 24 Aug 2009 12:20:09 -0700	[thread overview]
Message-ID: <000501ca24ef$e6444d20$b2cce760$@com> (raw)
In-Reply-To: <20090824100211.5c162f1a@Computername>

spamzad@googlemail.com wrote:
> ... /dev/mapper/home and then /home. Cryptsetup didn't recognize it
> as a luks-partition.
> ... same thing happened again
> ...
> martin@Computername:~$ cat /etc/fstab
> ...
> /dev/mapper/home        /home   ext3 defaults  0     2

I'm fairly new to LUKS, but are your sure about ext3?  I use ext2
throughout and so far, so good.


Using one identifier "home" in multiple contexts would confuse me, and
could be confusing some piece of software.  I try to use unique and
meaningful identifiers everywhere to keep things straight (especially
with multiple drives, LUKS, and LVM).


Here is an external drive that holds backup and archive images.  Note
the ext2 partition and ext2 file system, and related names /dev/sda1,
/dev/mapper/sda1_crypt, and /mnt/sda1_crypt:

    2009-08-24 11:38:58 root@p3600 ~/p3600
    # parted /dev/sda print
    Model: Seagate FreeAgent XTreme (scsi)
    Disk /dev/sda: 1500GB
    Sector size (logical/physical): 512B/512B
    Partition Table: msdos

    Number  Start  End     Size    Type     File system  Flags
     1      512B   1500GB  1500GB  primary  ext2


    2009-08-24 11:40:35 root@p3600 ~/p3600
    # fdisk -l /dev/sda

    Disk /dev/sda: 1500.3 GB, 1500301910016 bytes
    255 heads, 63 sectors/track, 182401 cylinders
    Units = cylinders of 16065 * 512 = 8225280 bytes
    Disk identifier: 0xb2dd7b60

       Device Boot      Start         End      Blocks   Id  System
    /dev/sda1               1      182402  1465138583+  83  Linux


    2009-08-24 11:42:53 root@p3600 ~/p3600
    # grep sda /etc/crypttab
    sda1_crypt /dev/sda1 /root/.luks/keyfile luks


    2009-08-24 11:44:07 root@p3600 ~/p3600
    # grep sda /etc/fstab
    /dev/mapper/sda1_crypt /mnt/sda1_crypt ext2 errors=remount-ro 0 2


    2009-08-24 11:45:53 root@p3600 ~/p3600
    # df /mnt/sda1_crypt/
    Filesystem        1K-blocks      Used Available Use% Mounted on
    /dev/mapper/sda1_crypt
                     1442147276 617075544 751814832  46% /mnt/sda1_crypt


    2009-08-24 11:45:58 root@p3600 ~/p3600
    # ll /mnt/sda1_crypt/
    total 28
    drwxr-xr-x 4 root root  4096 Jul 18 21:40 ./
    drwxr-xr-x 4 root root  4096 Jul 18 21:21 ../
    drwx------ 2 root root 16384 Jul 18 21:15 lost+found/
    drwxrwxrwx 9 root root  4096 Aug  9 13:27 q/


HTH,

David

  parent reply	other threads:[~2009-08-24 19:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-24  8:02 [dm-crypt] Broken header of a luks-partition - more than once spamzad
2009-08-24 15:55 ` Milan Broz
2009-08-24 22:50   ` Thomas Bächler
2009-08-24 23:10     ` Martin
     [not found]   ` <20090824180857.GB31701@tansi.org>
2009-08-25  3:08     ` Arno Wagner
2009-08-25  7:06       ` test532
2009-08-24 19:20 ` David Christensen [this message]
2009-08-24 20:29   ` Heinz Diehl

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='000501ca24ef$e6444d20$b2cce760$@com' \
    --to=dpchrist@holgerdanske.com \
    --cc=dm-crypt@saout.de \
    --cc=spamzad@googlemail.com \
    /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.