From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Dmitry Katsubo <dma_k@mail.ru>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: brtfs warning at ctree.h:1564 btrfs_update_device+0x220/0x230
Date: Wed, 17 Oct 2018 09:06:41 +0800 [thread overview]
Message-ID: <c9af2ee8-4148-957a-7e2e-a10f40a1dc00@gmx.com> (raw)
In-Reply-To: <e5970ef2-3d22-6c49-0634-8e6d9d92191d@mail.ru>
[-- Attachment #1.1: Type: text/plain, Size: 1025 bytes --]
On 2018/10/17 上午5:27, Dmitry Katsubo wrote:
> Dear btrfs team,
>
> I often observe kernel traces on linux-4.14.0 (mostly likely due to background
> "btrfs scrub") which contain the following "characterizing" line (for the rest
> see attachments):
>
> btrfs_remove_chunk+0x26a/0x7e0 [btrfs]
>
> I wonder if somebody from developers team knows anything about this problem. It
> seems like after such dump btfs volume continues to function OK.
It's a known minor problem.
"btrfs rescue fix-device-size <device>" could fix it offline (unmounted)
Or if you're using the fs as root fs, resize the fs by removing 4K would
also solve the problem:
# btrfs filesystem resize <devid>:-4K <mnt>
The cause is old mkfs/kernel isn't aligning device size correctly, while
later kernel is pretty picky about that alignment.
It's mostly a developer oriented warning, no harm except a lot of scary
kernel warning and may slow down log system.
Thanks,
Qu
>
> Thanks for any information!
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2018-10-17 1:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-16 21:27 brtfs warning at ctree.h:1564 btrfs_update_device+0x220/0x230 Dmitry Katsubo
2018-10-17 1:06 ` Qu Wenruo [this message]
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=c9af2ee8-4148-957a-7e2e-a10f40a1dc00@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=dma_k@mail.ru \
--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).