On Jun 9, 2013, at 6:44 AM, André Schlichting <an...@delorus.de> wrote: > > /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.
The end points are different according to information provided: >> The old partition had the sector boundaries: 245547520 - 732566527 >> I deleted this one and created a new one with boundaries: 33024 - 732566640 But also, the containing LUKS volume hasn't been grown yet. I wonder if it's a problem for the LUKS container to be on a much larger partition, not yet resized, and yet made active. It seems the LUKS volume was found and opened, which means all of its metadata is intact, but the resulting mounted (decrypted) block device is corrupt, although even though the LUKS device hasn't been resized I'd think you should still be able to mount the existing file system, but the resize wouldn't have been possible without first resizing the LUKS device. > > 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? I just did this without LUKS and it did work. Chris Murphy-- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
