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 12:44:23 +0200 [thread overview]
Message-ID: <51B45C87.2040308@delorus.de> (raw)
In-Reply-To: <8E5CABA3-602A-4D2F-AAEF-74F007F3C2FF@colorremedies.com>
Am 09.06.2013 00:57, schrieb Chris Murphy:
> The next issue:
>
>>> if=/dev/sdc2 skip=$((245547520-33024)) seek=0 of=/dev/sdc2
>
> You have a skip (skip n block from input) value well inside of sdc2. It seems you should have skipped from sdc not sdc2, and should have used the old start value for sdc2 which was just 245547520, and you needed to specify a count value in order to get the correct number of blocks, which would have been 732566527-245547520. Then write those blocks to sdc2 (which makes seek= unnecessary).
>
>
> Chris Murphy
>
/dev/sdc2 at this moment was already the new partition with boundaries
33024 to 732566640 with the old partition inside. Therefore I used
skip=old start - new start, which inside of sdc2 points to the start of
the old partition. I didn't worry about the count, because the partition
was at the end of the disk.
I actually think that the move of the partition was no problem. I guess
that btrfs has some absolute references which have to be adjusted and
now has some problems with sectors not at the right place. The following
error from btrfsck
> Check tree block failed, want=959572647936, have=13587293097915834379
suggests that 959572647936 is a way off...
Maybe first, the principal question: Can one just move a btrfs-partition
to the left by
* delete partition
* create partition moved
* dd data from old to new partition
Or does one have to adjust some references inside the btrfs filesystem?
next prev parent reply other threads:[~2013-06-09 10:44 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
2013-06-08 22:57 ` Chris Murphy
2013-06-09 10:44 ` André Schlichting [this message]
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=51B45C87.2040308@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 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.