Re: "BTRFS error (device vda1): couldn't get super buffer head for bytenr x"

[Nick Gilmour <nickeforos@gmail.com>]

> 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?

OK. I guess, this is it. I didn't do any 'btrfs filesystem resize' .
The guides I was following didn't mention something like that. I was
assuming that if it works for other FS like this it should also work
for BTRFS. So I have to run this one:

# btrfs filesystem resize -350g /home ?

Should it be before or after I shrink the .img?

> Is this before or after the resize?

 It's after the supposed resize. I shoud have seen that BTRFS didn't
notice the change...

On Sun, Oct 8, 2017 at 11:03 PM, Chris Murphy <lists@colorremedies.com> wrote:
> 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