Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: "André Schlichting" <andre@delorus.de>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Moved partition via dd
Date: Sun, 09 Jun 2013 00:42:01 +0200	[thread overview]
Message-ID: <51B3B339.4030108@delorus.de> (raw)
In-Reply-To: <E3D849EC-DDAC-4E05-9571-303B869F7A8D@colorremedies.com>

Am 09.06.2013 00:20, schrieb Chris Murphy:
>
> On Jun 8, 2013, at 8:47 AM, André Schlichting <andre@delorus.de> wrote:
>
>>
>> The old partition had the sector boundaries: 245547520 - 732566527
>>
>> I deleted this one and created a new one with boundaries: 33024 - 732566640
>>
>> Now I moved the data
>>   > sudo dd conv=notrunc bs=4096 iflag=fullblock if=/dev/sdc2 skip=$((245547520-33024)) seek=0 of=/dev/sdc2
>
> You ultimately moved the wrong data because bs=4096 for dd, yet the partition logical sectors are based on 512 bytes.
>
>
> Chris Murphy
>

I'm not sure, but this external disk has a GPT with sector size 4096 and 
as I wrote the dm-crypted LUKS container can be opened without complains.
 > fdisk -l /dev/sdc
WARNING: fdisk GPT support is currently new, and therefore in an 
experimental phase. Use at your own discretion.

Disk /dev/sdc: 3000.6 GB, 3000592982016 bytes, 732566646 sectors
Units = Sektoren of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk label type: gpt
#         Start          End    Size  Type            Name
  1            6        32773    128M  Microsoft reserved partition
  2        33024    732566640    2,7T  Linux filesystem

André Schlichting

  reply	other threads:[~2013-06-08 22:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-08 12:47 Moved partition via dd André Schlichting
2013-06-08 22:20 ` Chris Murphy
2013-06-08 22:42   ` André Schlichting [this message]
2013-06-08 22:57     ` Chris Murphy
2013-06-09 10:44       ` André Schlichting
2013-06-09 11:11         ` Hugo Mills
2013-06-09 17:05           ` André Schlichting
2013-06-09 20:09         ` Chris Murphy

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=51B3B339.4030108@delorus.de \
    --to=andre@delorus.de \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox