All of lore.kernel.org
 help / color / mirror / Atom feed
From: Liu Bo <bo.li.liu@oracle.com>
To: Nick Gilmour <nickeforos@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: "BTRFS error (device vda1): couldn't get super buffer head for bytenr x"
Date: Fri, 6 Oct 2017 17:08:37 -0700	[thread overview]
Message-ID: <20171007000837.GD19068@lim.localdomain> (raw)
In-Reply-To: <CAH-drow6AB9vu84DJGB90bbvE7DZnJ+eZOvJmxu9w1rHA5CrNA@mail.gmail.com>

On Fri, Oct 06, 2017 at 12:25:17PM +0200, Nick Gilmour wrote:
> Hi all,
> 
> I have converted .vdi disk (BTRFS) into a .img disk, resized it from
> 500GB to 150GB and then copied into a ZFS Volume. I've imported the VM
> into VMM and it started normally but an upgrade failed. I've rebooted
> and  got only a blue screen something like a BSOD on Windows. I've
> changed into a terminal and now this error appears constantly:
> 
>  "BTRFS error (device vda1): couldn't get super buffer head for bytenr x"

The error implies that it failed to read the sectors which contains
btrfs superblock, given you've shrinked the size, I guess btrfs
doesn't know that somehow and is trying to issue writes to a >150GB
position(could be 256G).

You can check that 'bytenr x'.

Which command did you use to resize it?

thanks,

-liubo

> 
> I can stop it shortly with Ctrl-C and enter a command. With startx I
> can see my desktop in blue  color with some icons in it and nothing
> more.
> 
> 
> uname -a
> Linux VM-Ubuntu 4.4.0-83-generic
> 
> btrfs --version
> btrfs-progs v4.4
> 
> 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
> 
> Label: 'extra' uuid: y
>            Total devices 1 FS bytes used 112.00KiB
>             devid 1 size 100.00 GiB used 2.02GiB path /dev/sdb1
> 
> btrfs fi df /home
> Data, single: total=106.40GiB, used=96.42GiB
> System, DUP: total=8.00MiB, used=48.00KiB
> Metadata, DUP: total=14.88GiB, used=11.18GiB
> GlobalReserve, single: total=512.00 MiB, used=0.00B
> 
> dmesg > dmesg.log
> compiz: segfault at ... error 4 in libnux-graphics-4.0.so...
> 
> 
> Any ideas?
> 
> Regards,
> Nick
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2017-10-07  0:12 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 [this message]
2017-10-08 15:39   ` Nick Gilmour
2017-10-08 21:03     ` Chris Murphy
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=20171007000837.GD19068@lim.localdomain \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.