All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Richards <paul.richards@gmail.com>
To: Patrik Lundquist <patrik.lundquist@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: fs/btrfs/ctree.h:1559 warnings
Date: Sat, 28 Apr 2018 21:16:58 +0100	[thread overview]
Message-ID: <CAMoswejKgjw+ktxc7iGX9m6F-n5Xq_=kzyLiR4xYUf2s=bYaDA@mail.gmail.com> (raw)
In-Reply-To: <CAA7pwKOGS1MfwiO7AvfGPMP5ddhA6EMF+u3eZ+yE++RYvM=bfg@mail.gmail.com>

On 28 April 2018 at 20:39, Patrik Lundquist <patrik.lundquist@gmail.com> wrote:
> On 28 April 2018 at 20:54, Paul Richards <paul.richards@gmail.com> wrote:
>>
>> Hi,
>> I recently upgraded from Linux 4.4.0 to 4.13.0 (Ubuntu 16.04 stock to
>> hwe kernel).
>>
>> Since then, I've noticed lots of btrfs warnings in dmesg (example at
>> the end).  I believe these warnings to be benign, and they relate to
>> my partition not being a multiple of 4KiB in size (I confirmed that
>> alignment is okay in this instance).
>
>
> Run btrfs rescue fix-device-size <device>.
>


Excellent, that looks like exactly what I need.  It's a shame my
google-fu didn't uncover it before I posted.

However, the "fix-device-size" sub-command is not available in
btrfs-tools (v4.4) from Ubuntu 16.04.  I guess my original question
still stands.  Is this warning safe for me to ignore?


I will likely upgrade to Ubuntu 18.04 in a few months at which point
I'll get a newer btrfs-tools, but until then can I safely ignore this
warning?

  parent reply	other threads:[~2018-04-28 20:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-28 18:54 fs/btrfs/ctree.h:1559 warnings Paul Richards
     [not found] ` <CAA7pwKOGS1MfwiO7AvfGPMP5ddhA6EMF+u3eZ+yE++RYvM=bfg@mail.gmail.com>
2018-04-28 20:16   ` Paul Richards [this message]
2018-04-29  1:50     ` Qu Wenruo
2018-05-02 19:43       ` Paul Richards
2018-05-02 19:45         ` Paul Richards

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='CAMoswejKgjw+ktxc7iGX9m6F-n5Xq_=kzyLiR4xYUf2s=bYaDA@mail.gmail.com' \
    --to=paul.richards@gmail.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=patrik.lundquist@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.