From: Greg KH <gregkh@linuxfoundation.org>
To: Kyle Sanderson <kyle.leet@gmail.com>
Cc: linux-btrfs@vger.kernel.org,
Linux-Kernal <linux-kernel@vger.kernel.org>,
linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: btrfs induced data loss (on xfs) - 5.19.0-38-generic
Date: Mon, 17 Apr 2023 08:01:06 +0200 [thread overview]
Message-ID: <ZDzgojYAZXS_D_OH@kroah.com> (raw)
In-Reply-To: <CACsaVZJGPux1yhrMWnq+7nt3Zz5wZ6zEo2+S2pf=4czpYLFyjg@mail.gmail.com>
On Sun, Apr 16, 2023 at 10:20:45PM -0700, Kyle Sanderson wrote:
> The single btrfs disk was at 100% utilization and a wa of 50~, reading
> back at around 2MB/s. df and similar would simply freeze. Leading up
> to this I removed around 2T of data from a single btrfs disk. I
> managed to get most of the services shutdown and disks unmounted, but
> when the system came back up I had to use xfs_repair (for the first
> time in a very long time) to boot into my system. I likely should have
> just pulled the power...
>
> [1147997.255020] INFO: task happywriter:3425205 blocked for more than
> 120 seconds.
> [1147997.255088] Not tainted 5.19.0-38-generic #39~22.04.1-Ubuntu
This is a distro-specific kernel, sorry, nothing to do with our releases
as the 5.19 kernel branch is long end-of-life. Please work with your
distro for this issue if you wish to stick to this kernel version.
good luck!
greg k-h
next prev parent reply other threads:[~2023-04-17 6:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 5:20 Kyle Sanderson
2023-04-17 6:01 ` Greg KH [this message]
2023-04-17 6:07 ` Kyle Sanderson
2023-04-17 8:42 ` Qu Wenruo
2023-04-18 7:07 ` Kyle Sanderson
2023-04-18 7:18 ` Qu Wenruo
2023-04-18 7:31 ` Kyle Sanderson
2023-04-18 8:00 ` Qu Wenruo
2023-04-19 1:55 ` Dave Chinner
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=ZDzgojYAZXS_D_OH@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kyle.leet@gmail.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®