From: Wang Yugui <wangyugui@e16-tech.com>
To: Thomas <74cmonty@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 2702175, rd 2719033, flush 0, corrupt 6, gen 0
Date: Sat, 13 Mar 2021 15:21:50 +0800 [thread overview]
Message-ID: <20210313152146.1D7D.409509F4@e16-tech.com> (raw)
In-Reply-To: <ef3da480-d00d-877e-2349-6d7b2ebda05e@gmail.com>
Hi,
If there is some partition size change after filesystem created,
'btrfs filesystem resize max' will help.
See also
https://lore.kernel.org/linux-btrfs/42d37a6393db7ad5d83bc167459c8a5c@steev.me.uk/T/#t
Best Regards
Wang Yugui (wangyugui@e16-tech.com)
2021/03/12
> Hello,
>
> I have observed this error messages in systemd journal:
> BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 2702175, rd 2719033,
> flush 0, corrupt 6, gen 0
>
> Here are the bottom lines of journalctl -xb:
> ?r 12 08:30:41 pc1-desktop kernel: attempt to access beyond end of device
> ???????????????????????????????????? sdb1: rw=524288, want=497859712,
> limit=496091703
> M?r 12 08:30:41 pc1-desktop kernel: attempt to access beyond end of device
> ???????????????????????????????????? sdb1: rw=524288, want=497859840,
> limit=496091703
> M?r 12 08:30:41 pc1-desktop kernel: attempt to access beyond end of device
> ???????????????????????????????????? sdb1: rw=256, want=497859704,
> limit=496091703
> M?r 12 08:30:41 pc1-desktop kernel: BTRFS error (device sda1): bdev
> /dev/sdb1 errs: wr 2702175, rd 2719033, flush 0, corrupt 6, gen 0
> M?r 12 08:30:41 pc1-desktop kernel: attempt to access beyond end of device
> ???????????????????????????????????? sdb1: rw=256, want=497859720,
> limit=496091703
> M?r 12 08:30:41 pc1-desktop kernel: attempt to access beyond end of device
> ???????????????????????????????????? sdb1: rw=524288, want=497859968,
> limit=496091703
> M?r 12 08:30:41 pc1-desktop kernel: BTRFS error (device sda1): bdev
> /dev/sdb1 errs: wr 2702175, rd 2719034, flush 0, corrupt 6, gen 0
> M?r 12 08:30:41 pc1-desktop kernel: attempt to access beyond end of device
> ???????????????????????????????????? sdb1: rw=256, want=497859728,
> limit=496091703
> M?r 12 08:30:41 pc1-desktop kernel: attempt to access beyond end of device
> ???????????????????????????????????? sdb1: rw=256, want=497859712,
> limit=496091703
> M?r 12 08:30:41 pc1-desktop kernel: BTRFS error (device sda1): bdev
> /dev/sdb1 errs: wr 2702175, rd 2719035, flush 0, corrupt 6, gen 0
> M?r 12 08:30:41 pc1-desktop kernel: attempt to access beyond end of device
> ???????????????????????????????????? sdb1: rw=524288, want=497860096,
> limit=496091703
> M?r 12 08:30:41 pc1-desktop kernel: BTRFS error (device sda1): bdev
> /dev/sdb1 errs: wr 2702175, rd 2719036, flush 0, corrupt 6, gen 0
> M?r 12 08:30:41 pc1-desktop kernel: attempt to access beyond end of device
> ???????????????????????????????????? sdb1: rw=256, want=497859736,
> limit=496091703
> M?r 12 08:30:41 pc1-desktop kernel: attempt to access beyond end of device
> ???????????????????????????????????? sdb1: rw=256, want=497859848,
> limit=496091703
> M?r 12 08:30:41 pc1-desktop kernel: BTRFS error (device sda1): bdev
> /dev/sdb1 errs: wr 2702175, rd 2719037, flush 0, corrupt 6, gen 0
> M?r 12 08:30:41 pc1-desktop kernel: BTRFS error (device sda1): bdev
> /dev/sdb1 errs: wr 2702175, rd 2719038, flush 0, corrupt 6, gen 0
> M?r 12 08:30:41 pc1-desktop kernel: BTRFS error (device sda1): bdev
> /dev/sdb1 errs: wr 2702175, rd 2719039, flush 0, corrupt 6, gen 0
> M?r 12 08:30:41 pc1-desktop kernel: BTRFS error (device sda1): bdev
> /dev/sdb1 errs: wr 2702175, rd 2719040, flush 0, corrupt 6, gen 0
> M?r 12 08:30:41 pc1-desktop kernel: BTRFS error (device sda1): bdev
> /dev/sdb1 errs: wr 2702175, rd 2719041, flush 0, corrupt 6, gen 0
>
>
> I have configured a multidrive setup with 2 identical SSDs.
>
> [root@pc1-desktop ~]# uname -a
> Linux pc1-desktop 5.10.22-2-lts #1 SMP Wed, 10 Mar 2021 10:30:57 +0000
> x86_64 GNU/Linux
> [root@pc1-desktop ~]# btrfs --version
> btrfs-progs v5.11
> [root@pc1-desktop ~]# btrfs fi show
> Label: 'archlinux'? uuid: 78462a70-55ad-4444-9d91-e71e42cce51c
> ??? Total devices 2 FS bytes used 178.93GiB
> ??? devid??? 1 size 236.55GiB used 233.50GiB path /dev/sda1
> ??? devid??? 2 size 238.47GiB used 233.50GiB path /dev/sdb1
>
> Label: 'backup'? uuid: de094dc0-58b7-4931-b948-4b920495bf94
> ??? Total devices 1 FS bytes used 210.97GiB
> ??? devid??? 1 size 232.89GiB used 228.87GiB path /dev/sdd
>
> [root@pc1-desktop ~]# btrfs fi df /
> Data, RAID1: total=229.47GiB, used=175.82GiB
> System, RAID1: total=32.00MiB, used=64.00KiB
> Metadata, RAID1: total=4.00GiB, used=3.11GiB
> GlobalReserve, single: total=512.00MiB, used=0.00B
>
>
> Can you please advise how to fix these errors?
>
>
> Regards
> Thomas
next prev parent reply other threads:[~2021-03-13 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 7:47 BTRFS error (device sda1): bdev /dev/sdb1 errs: wr 2702175, rd 2719033, flush 0, corrupt 6, gen 0 Thomas
2021-03-13 6:59 ` Chris Murphy
2021-03-13 7:21 ` Wang Yugui [this message]
2021-03-13 12:21 ` Thomas
2021-03-13 18:02 ` Chris Murphy
2021-03-20 9:53 ` Thomas Schneider
2021-04-02 20:46 ` Thomas
2021-04-03 17:28 ` Lukas Straub
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=20210313152146.1D7D.409509F4@e16-tech.com \
--to=wangyugui@e16-tech.com \
--cc=74cmonty@gmail.com \
--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).