From: Michael Ruiz <michael@mruiz.dev>
To: linux-btrfs@vger.kernel.org
Subject: Re: Error during balancing '/': Input/output error
Date: Sat, 28 Dec 2019 01:53:55 -0800 [thread overview]
Message-ID: <2135877.ElGaqSPkdT@archlinux> (raw)
In-Reply-To: <4196932.LvFx2qVVIh@archlinux>
[-- Attachment #1: Type: text/plain, Size: 2494 bytes --]
> There are quite some reports about this problem. So far no real
> corrupted confirmed.
>
> You can confirm it by scrub.
>
> I'm afraid there is some bug in data balance code which leads to this.
> We will dig further to pin down the cause.
>
> BTW, does that problem always show up at block group 253562454016? Or it
> randomly shows up at different block groups?
>
> Thanks,
> Qu
Hi Qu,
It appears to be the same data blocks giving me this issue. I have tried it
while mounting from a bootable usb and in my arch linux install both with
similar results. I should also mention I have a btrfs root partition within a
luks lvm partition becuase btrfs provides no encryption. I'm not sure this
makes a difference. Would you suggest running somekind of disk check or by
running scrub? Please let me know what I should try to resolve this.
谢谢
``` BEGIN DEBUG INFO ```
ERROR: error during balancing '/': Input/output error
[michael@linux /]$ dmesg | tail
[ 462.460626] audit: type=1104 audit(1577525576.905:124): pid=3415 uid=0
auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit,pam_env
acct="root" exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/2
res=success'
[ 465.880807] BTRFS info (device dm-1): found 25 extents
[ 470.501319] BTRFS info (device dm-1): found 25 extents
[ 471.713073] BTRFS info (device dm-1): relocating block group 253562454016
flags data
[ 472.251356] BTRFS warning (device dm-1): csum failed root -9 ino 262 off
1048576 csum 0x9a7afaa8 expected csum 0x63e15594 mirror 1
[ 472.254390] BTRFS warning (device dm-1): csum failed root -9 ino 262 off
1048576 csum 0x9a7afaa8 expected csum 0x63e15594 mirror 1
[ 472.716215] BTRFS info (device dm-1): balance: ended with status: -5
[ 473.122721] audit: type=1106 audit(1577525587.565:125): pid=2775 uid=0
auid=1000 ses=1 msg='op=PAM:session_close
grantors=pam_limits,pam_unix,pam_permit acct="root" exe="/usr/bin/sudo"
hostname=? addr=? terminal=/dev/pts/3 res=success'
[ 473.122840] audit: type=1104 audit(1577525587.565:126): pid=2775 uid=0
auid=1000 ses=1 msg='op=PAM:setcred grantors=pam_unix,pam_permit acct="root"
exe="/usr/bin/sudo" hostname=? addr=? terminal=/dev/pts/3 res=success'
[ 629.160619] audit: type=1131 audit(1577525743.603:127): pid=1 uid=0
auid=4294967295 ses=4294967295 msg='unit=packagekit comm="systemd" exe="/usr/
lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
``` END DEBUG INFO ```
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2019-12-28 9:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 12:39 Error during balancing '/': Input/output error Michael Ruiz
2019-12-27 13:21 ` Qu Wenruo
[not found] ` <5555870.lOV4Wx5bFT@archlinux>
2019-12-28 10:09 ` Qu Wenruo
2019-12-28 11:26 ` Michael Ruiz
2019-12-28 11:38 ` Qu Wenruo
2019-12-28 11:45 ` Michael Ruiz
2019-12-28 12:05 ` Qu Wenruo
2019-12-28 12:28 ` Michael Ruiz
2019-12-28 9:53 ` Michael Ruiz [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=2135877.ElGaqSPkdT@archlinux \
--to=michael@mruiz.dev \
--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