From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi0-f43.google.com ([209.85.218.43]:48247 "EHLO mail-oi0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751537AbdJHVDq (ORCPT ); Sun, 8 Oct 2017 17:03:46 -0400 Received: by mail-oi0-f43.google.com with SMTP id m198so24339988oig.5 for ; Sun, 08 Oct 2017 14:03:46 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <20171007000837.GD19068@lim.localdomain> From: Chris Murphy Date: Sun, 8 Oct 2017 22:03:45 +0100 Message-ID: Subject: Re: "BTRFS error (device vda1): couldn't get super buffer head for bytenr x" To: Nick Gilmour Cc: Liu Bo , Btrfs BTRFS Content-Type: text/plain; charset="UTF-8" Sender: linux-btrfs-owner@vger.kernel.org List-ID: On Sun, Oct 8, 2017 at 4:39 PM, Nick Gilmour wrote: > Thanks for the reply! > > For conversion I used this command: > $ vboxmanage internalcommands converttoraw mydisk.vdi mydisk.img > > and for resizing this one: > $ qemu-img resize mydisk.img 150G > > Is there something I can do to fix this or another way to do the > resizing without getting an error? I don't see a 'btrfs filesystem resize' command in your sequence. Did you actually resize the file system before you resized the underlying (virtual) block device? >>> btrfs fi show >>> Label: none uuid: x >>> Total devices 1 FS bytes used 473.68GiB >>> devid 1 size 492.00 GiB used 492.00GiB path /dev/sda1 Is this before or after the resize? -- Chris Murphy