linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs warnings in kernel 4.13.5
Date: Fri, 13 Oct 2017 11:02:07 +0000 (UTC)	[thread overview]
Message-ID: <pan$2aa3b$47885ead$d44bbe7e$37d6c337@cox.net> (raw)
In-Reply-To: CAC+fKQXPGpwuhVz7oNLzPLd0ydo+kiqG1vpcWvx+-DZ+2jL6Bg@mail.gmail.com

Juan Orti Alcaine posted on Fri, 13 Oct 2017 10:40:20 +0200 as excerpted:

> Hi,
> 
> I've upgraded my system to Fedora 27 and now I see many btrfs warnings,
> although the system seems to be working fine. Is this something I should
> worry about?

> # uname -a Linux xenon 4.13.5-300.fc27.x86_64 #1 SMP Thu Oct 5 16:57:11
> UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
> 
> # btrfs --version btrfs-progs v4.13.2

> [  337.813416] ------------[ cut here ]------------
> [  337.813453] WARNING: CPU: 5 PID: 459 at fs/btrfs/ctree.h:1559
> btrfs_update_device+0x1be/0x1d0 [btrfs]

> [  337.814256] ------------[ cut here ]------------
> [  337.814281] WARNING: CPU: 5 PID: 459 at fs/btrfs/ctree.h:1559
> btrfs_update_device+0x1be/0x1d0 [btrfs]

> [  337.822161] ------------[ cut here ]------------
> [  337.822185] WARNING: CPU: 5 PID: 459 at fs/btrfs/ctree.h:1559
> btrfs_update_device+0x1be/0x1d0 [btrfs]

> [  337.822868] ------------[ cut here ]------------
> [  337.822890] WARNING: CPU: 5 PID: 459 at fs/btrfs/ctree.h:1559
> btrfs_update_device+0x1be/0x1d0 [btrfs]


Those warnings aren't anything to be /too/ worried about.  They are 
triggered when a btrfs device size isn't a multiple of the btrfs 
sectorsize (currently 4 KiB on amd64 aka x86_64).  You can manually 
shrink your btrfs devices the fraction to an exact 4 KiB multiple, or 
wait a bit, and a new release of btrfs-tools should have a command to do 
it for you. 

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


  parent reply	other threads:[~2017-10-13 11:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-13  8:40 Btrfs warnings in kernel 4.13.5 Juan Orti Alcaine
2017-10-13  8:57 ` Juan Orti Alcaine
2017-10-13 11:02 ` Duncan [this message]
2017-10-13 12:06   ` Juan Orti Alcaine
2017-10-13 18:15   ` Chris Murphy
2017-10-13 21:57     ` Juan Orti Alcaine

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='pan$2aa3b$47885ead$d44bbe7e$37d6c337@cox.net' \
    --to=1i5t5.duncan@cox.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).