[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230419015512.GI447837@dread.disaster.area>
Date: Wed, 19 Apr 2023 11:55:12 +1000
From: Dave Chinner <david@...morbit.com>
To: Kyle Sanderson <kyle.leet@...il.com>
Cc: linux-btrfs@...r.kernel.org,
Linux-Kernal <linux-kernel@...r.kernel.org>,
linux-block@...r.kernel.org, linux-fsdevel@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: btrfs induced data loss (on xfs) - 5.19.0-38-generic
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@...morbit.com
Powered by blists - more mailing lists