linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
	linux-btrfs@vger.kernel.org
Subject: Re: call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device
Date: Thu, 28 Jun 2018 16:25:57 +0300	[thread overview]
Message-ID: <a80da87b-6c38-3b37-542c-17718bad8d5c@suse.com> (raw)
In-Reply-To: <50443c666dc4509d74f9f23d7012080845a20940.camel@scientia.net>



On 28.06.2018 16:19, Christoph Anton Mitterer wrote:
> Hey.
> 
> On a 4.16.16 kernel with a RAID 1 btrfs I got the following messages
> since today.
> 
> Data seems still to be readable (correctly)... and there are no other
> errors (like SATA errors) in the kernel log.
> 
> Any idea what these could mean?

It means you have a device, whose size is not aligned to 4k. You can fix
this either by resizing the device to be properly aligned to a 4k
boundary (if you are on x86) or better yet, just run :


btrfs rescue fix-device-size /dev/<device to fix>

> 
> Thanks,
> Chris.

  reply	other threads:[~2018-06-28 19:03 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 13:19 call trace: WARNING: at /build/linux-uwVqDp/linux-4.16.16/fs/btrfs/ctree.h:1565 btrfs_update_device Christoph Anton Mitterer
2018-06-28 13:25 ` Nikolay Borisov [this message]
2018-06-28 14:09 ` Qu Wenruo
2018-06-28 14:17   ` Christoph Anton Mitterer
2018-06-28 14:25     ` Nikolay Borisov
2018-06-28 14:58     ` Qu Wenruo
2018-06-29  1:05       ` Christoph Anton Mitterer
2018-06-29  1:10         ` Qu Wenruo
2018-06-29 12:55           ` Christoph Anton Mitterer

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=a80da87b-6c38-3b37-542c-17718bad8d5c@suse.com \
    --to=nborisov@suse.com \
    --cc=calestyo@scientia.net \
    --cc=linux-btrfs@vger.kernel.org \
    /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).