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?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
