From: Chris Murphy <lists@colorremedies.com>
To: Nick Gilmour <nickeforos@gmail.com>
Cc: Liu Bo <bo.li.liu@oracle.com>, Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: "BTRFS error (device vda1): couldn't get super buffer head for bytenr x"
Date: Sun, 8 Oct 2017 22:03:45 +0100 [thread overview]
Message-ID: <CAJCQCtRYkEQzCVqTbeE5cxOffFmqB5TFoU5wXaneZ+34NefaFA@mail.gmail.com> (raw)
In-Reply-To: <CAH-droxSCv9CfPE2gDAmmDV33ucjh7nABNvmv=fsCzdewcm7rQ@mail.gmail.com>
On Sun, Oct 8, 2017 at 4:39 PM, Nick Gilmour <nickeforos@gmail.com> 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
next prev parent reply other threads:[~2017-10-08 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 10:25 "BTRFS error (device vda1): couldn't get super buffer head for bytenr x" Nick Gilmour
2017-10-07 0:08 ` Liu Bo
2017-10-08 15:39 ` Nick Gilmour
2017-10-08 21:03 ` Chris Murphy [this message]
2017-10-09 0:26 ` Nick Gilmour
[not found] ` <CAH-drozNA1N6xO2dAknLD-JQu75BAEi+GpiEibA-R-Zk1U7xmA@mail.gmail.com>
2017-10-09 9:28 ` Chris Murphy
[not found] ` <CAH-drozVaiXMoXqs8hiHvd5n8qDvbGLnp=1OPndsibhxjGkNxw@mail.gmail.com>
[not found] ` <59df4db2.8508370a.40c79.2c64.GMRIR@mx.google.com>
2017-10-12 11:12 ` Delivery Status Notification (Failure) Nick Gilmour
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=CAJCQCtRYkEQzCVqTbeE5cxOffFmqB5TFoU5wXaneZ+34NefaFA@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=bo.li.liu@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nickeforos@gmail.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;
as well as URLs for NNTP newsgroup(s).