From: "Hendrik Friedel" <hendrik@friedels.name>
To: "Chris Murphy" <lists@colorremedies.com>,
"Btrfs BTRFS" <linux-btrfs@vger.kernel.org>
Subject: Re[2]: Filesystem sometimes Hangs
Date: Tue, 30 Mar 2021 12:50:56 +0000 [thread overview]
Message-ID: <em7b647410-6346-4e95-b97a-f45ee2de0037@desktop-g0r648m> (raw)
In-Reply-To: <CAJCQCtQt83dXev6Ngo_tDPZFqD60eD3W3h-1ZT8KLc5hMcB_HA@mail.gmail.com>
Hello,
thanks for your reply, Chris.
>> [Mo Mär 29 09:29:22 2021] BTRFS info (device sda1): bdev /dev/sda1 errs:
>> wr 133, rd 133, flush 0, corrupt 0, gen 1
>>
>> Maybe, the last line is concerning?
>
>Yes. Do a 'btrfs scrub' and check dmesg for detailed errors.
[Mo Mär 29 09:29:22 2021] BTRFS info (device sda1): bdev /dev/sda1 errs: wr 133, rd 133, flush 0, corrupt 0, gen 1
[Mo Mär 29 13:10:39 2021] BTRFS info (device sda1): scrub: started on devid 1
[Mo Mär 29 13:10:39 2021] BTRFS info (device sda1): scrub: started on devid 2
[Mo Mär 29 23:30:49 2021] BTRFS info (device sda1): scrub: not finished on devid 2 with status: -125
[Mo Mär 29 23:30:50 2021] BTRFS info (device sda1): scrub: not finished on devid 1 with status: -125
[Di Mär 30 00:04:07 2021] BTRFS info (device sda1): scrub: started on devid 1
[Di Mär 30 00:04:07 2021] BTRFS info (device sda1): scrub: started on devid 2
[Di Mär 30 02:50:09 2021] BTRFS info (device sda1): scrub: finished on devid 1 with status: 0
[Di Mär 30 04:36:59 2021] BTRFS info (device sda1): scrub: finished on devid 2 with status: 0
There is nothing more, related to btrfs.
What I find in syslog:
Mar 28 20:28:21 homeserver kernel: [1298340.851140] INFO: task btrfs-cleaner:20078 blocked for more than 241 seconds.
Mar 28 20:28:21 homeserver kernel: [1298340.854109] task:btrfs-cleaner state:D stack: 0 pid:20078 ppid: 2 flags:0x00004000
Mar 28 20:28:21 homeserver kernel: [1298340.854151] wait_current_trans+0xc2/0x120 [btrfs]
Mar 28 20:28:21 homeserver kernel: [1298340.854169] start_transaction+0x46d/0x540 [btrfs]
Mar 28 20:28:21 homeserver kernel: [1298340.854183] btrfs_drop_snapshot+0x90/0x7f0 [btrfs]
Mar 28 20:28:21 homeserver kernel: [1298340.854202] ? btrfs_delete_unused_bgs+0x3e/0x850 [btrfs]
Mar 28 20:28:21 homeserver kernel: [1298340.854218] btrfs_clean_one_deleted_snapshot+0xd7/0x130 [btrfs]
Mar 28 20:28:21 homeserver kernel: [1298340.854232] cleaner_kthread+0xfa/0x120 [btrfs]
Mar 28 20:28:21 homeserver kernel: [1298340.854247] ? btrfs_alloc_root+0x3d0/0x3d0 [btrfs]
Mar 28 20:28:21 homeserver kernel: [1298340.857610] wait_current_trans+0xc2/0x120 [btrfs]
Mar 28 20:28:21 homeserver kernel: [1298340.857627] start_transaction+0x46d/0x540 [btrfs]
Mar 28 20:28:21 homeserver kernel: [1298340.857643] btrfs_create+0x58/0x1f0 [btrfs]
> Next
>'btrfs check --readonly' (must be done offline ie booted from usb
>stick). And if it all comes up without errors or problems, you can
>zero the statistics with 'btrfs dev stats -z'.
No error found. Neither in btrfs check, nor in scrub.
So, shall I reset the stats then?
>But otherwise we need
>to see the errors to know what's going wrong. It's not normal to have
>either read or write errors. It could be related to the problem, or an
>additional problem.
>
>> Mar 28 20:58:34 homeserver kernel: [1300153.336273] ?
>> btrfs_cleanup_transaction+0x590/0x590 [btrfs]
>>
>>
>> What could I do to find the cause?
>
>What kernel version?
5.10.0-0.bpo.3-amd64
Best regards,
Hendrik
next prev parent reply other threads:[~2021-03-30 12:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 11:11 Filesystem sometimes Hangs Hendrik Friedel
2021-03-29 18:07 ` Chris Murphy
2021-03-30 12:50 ` Hendrik Friedel [this message]
2021-03-31 6:27 ` Re[2]: " Chris Murphy
2021-03-31 14:03 ` Re[4]: " Hendrik Friedel
2021-03-31 20:11 ` Chris Murphy
2021-04-03 16:12 ` Re[6]: " Hendrik Friedel
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=em7b647410-6346-4e95-b97a-f45ee2de0037@desktop-g0r648m \
--to=hendrik@friedels.name \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.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).