From: Dave Chinner <david@fromorbit.com>
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>,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: btrfs induced data loss (on xfs) - 5.19.0-38-generic
Date: Wed, 19 Apr 2023 11:55:12 +1000 [thread overview]
Message-ID: <20230419015512.GI447837@dread.disaster.area> (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
What exactly was the error messages XFS emitted when it failed to
mount, and what did xfs_repair fix to enable it to boot? Unless you
have a broken disk (i.e. firmware either lies about cache flush
completion or the implementation is broken), there is no reason for
any amount of load on the disk to cause filesystem corruption....
-Dave.
--
Dave Chinner
david@fromorbit.com
prev parent reply other threads:[~2023-04-19 1:55 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
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 [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=20230419015512.GI447837@dread.disaster.area \
--to=david@fromorbit.com \
--cc=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®