linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Rich Rauenzahn <rrauenza@gmail.com>,
	Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: WARNING: CPU: 3 PID: 439 at fs/btrfs/ctree.h:1559 btrfs_update_device+0x1c5/0x1d0 [btrfs]
Date: Wed, 28 Aug 2019 22:21:23 +0800	[thread overview]
Message-ID: <2a8f9cce-eef0-6e21-eea5-0aa9eaf4bd83@gmx.com> (raw)
In-Reply-To: <CAG+QAKXTRiC0s5pH_EQoz7Zd7nNfMC5++AN+EFgU6yY=3uvckw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3218 bytes --]



On 2017/9/19 下午11:56, Rich Rauenzahn wrote:
> I've filed a bug on this kernel trace -- I get 100's of these a day.
> I'd like to make them go away ....

If you want to solve the problem sooner, then mail list is faster than
kernel bugzilla.

For your case, it's just a warning for unaligned device size, normally
caused by older mkfs or older kernel.

You can fix it by using "btrfs rescue fix-device-size <device>" on a
unmounted fs, or use "btrfs resize <devid>:-4K <mnt>" to resize *each*
device of your mounted fs.

I'd prefer "btrfs rescue fix-device-size <device>" if you have the
latest version of btrfs-progs, as it does not only fix the unaligned
device size, but also fix your super block total bytes.

Thanks,
Qu
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=196949
> 
> [    4.747356] ------------[ cut here ]------------
> [    4.747377] WARNING: CPU: 3 PID: 439 at fs/btrfs/ctree.h:1559
> btrfs_update_device+0x1c5/0x1d0 [btrfs]
> [    4.747377] Modules linked in: nfs_acl lockd grace sunrpc ip_tables
> btrfs xor raid6_pq sd_mod crc32c_intel firewire_ohci igb ahci
>  firewire_core crc_itu_t dca libahci i915 libata i2c_algo_bit e1000e
> drm_kms_helper ptp syscopyarea sysfillrect pps_core sysimgblt f
> b_sys_fops drm video
> [    4.747385] CPU: 3 PID: 439 Comm: btrfs-cleaner Not tainted
> 4.13.2-1.el7.elrepo.x86_64 #1
> [    4.747385] Hardware name: Supermicro X10SAE/X10SAE, BIOS 2.0a 05/09/2014
> [    4.747386] task: ffff88040cdcae80 task.stack: ffffc900021f4000
> [    4.747396] RIP: 0010:btrfs_update_device+0x1c5/0x1d0 [btrfs]
> [    4.747396] RSP: 0018:ffffc900021f7d00 EFLAGS: 00010206
> [    4.747397] RAX: 0000000000000fff RBX: ffff880407b7aa80 RCX: 0000001bc6c71e00
> [    4.747397] RDX: ffff880000000000 RSI: ffff880404cd3f3c RDI: ffff880409417b58
> [    4.747398] RBP: ffffc900021f7d48 R08: 0000000000003f60 R09: ffffc900021f7cb8
> [    4.747398] R10: 0000000000001000 R11: 0000000000000003 R12: ffff88040559f800
> [    4.747398] R13: 0000000000000000 R14: ffff880409417b58 R15: 0000000000003f3c
> [    4.747399] FS:  0000000000000000(0000) GS:ffff88041fac0000(0000)
> knlGS:0000000000000000
> [    4.747399] CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> [    4.747400] CR2: 00007f29c3000248 CR3: 00000004056a4000 CR4: 00000000001406e0
> [    4.747400] Call Trace:
> [    4.747410]  btrfs_remove_chunk+0x2fb/0x8b0 [btrfs]
> [    4.747418]  btrfs_delete_unused_bgs+0x363/0x440 [btrfs]
> [    4.747426]  cleaner_kthread+0x150/0x180 [btrfs]
> [    4.747429]  kthread+0x109/0x140
> [    4.747436]  ? btree_invalidatepage+0xa0/0xa0 [btrfs]
> [    4.747437]  ? kthread_park+0x60/0x60
> [    4.747439]  ret_from_fork+0x25/0x30
> [    4.747439] Code: 10 00 00 00 4c 89 fe e8 8a 30 ff ff 4c 89 f7 e8
> 32 f6 fc ff e9 d3 fe ff ff b8 f4 ff ff ff e9 d4 fe ff ff 0f 1f 00 e8
> bb 2e 9e e0 <0f> ff eb af 0f 1f 80 00 00 00 00 0f 1f 44 00 00 55 31 d2
> be 02
> [    4.747450] ---[ end trace 1ef80a625983d73b ]---
> --
> 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
> 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2019-08-28 14:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-19 15:56 WARNING: CPU: 3 PID: 439 at fs/btrfs/ctree.h:1559 btrfs_update_device+0x1c5/0x1d0 [btrfs] Rich Rauenzahn
2017-09-20  0:31 ` Qu Wenruo
2017-09-20  4:49   ` Rich Rauenzahn
2017-09-20  4:59     ` Qu Wenruo
2017-09-20  5:10       ` Qu Wenruo
2017-09-20  5:39         ` Qu Wenruo
2017-09-20  6:11           ` nborisov
2017-09-20  6:23             ` Qu Wenruo
2017-09-20 14:14               ` nborisov
2017-09-20 14:42                 ` Qu Wenruo
2017-09-20 16:53                 ` Rich Rauenzahn
2017-09-20 16:58           ` Rich Rauenzahn
2017-09-20 18:10             ` Rich Rauenzahn
2017-09-20 23:19               ` Qu Wenruo
2019-08-28 14:21 ` 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=2a8f9cce-eef0-6e21-eea5-0aa9eaf4bd83@gmx.com \
    --to=quwenruo.btrfs@gmx.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rrauenza@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 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).