Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Thu, 24 Jun 2021 14:12:56 +0200
From:   David Sterba <dsterba@suse.cz>
To:     Benjamin LaHaise <ben@communityfibre.ca>
Cc:     linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: linux-mm@kvack.org - limping on a backup
Message-ID: <20210624121256.GS28158@twin.jikos.cz>
Reply-To: dsterba@suse.cz
Mail-Followup-To: dsterba@suse.cz, Benjamin LaHaise <ben@communityfibre.ca>,
        linux-mm@kvack.org, linux-kernel@vger.kernel.org
References: <20210622145954.GA4058@kvack.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20210622145954.GA4058@kvack.org>
User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12)
Precedence: bulk

On Tue, Jun 22, 2021 at 10:59:54AM -0400, Benjamin LaHaise wrote:
> FYI: the filesystem hosting kanga.kvack.org which hosts linux-mm@kvack.org
> and a few other assorted things was damaged around 9:17am.  The mailing
> list is back up and running from a March 2nd backup for now.  The problem
> is either a bad SSD or a btrfs bug, however no crash dump was captured to 
> help with debugging.

Do you have any logs? Also when you have a suspicion that it was caused
by hardware, what's the SSD type? If you'd like a more interactive
discussion please come to the libera.chat #btrfs channel, there are
people with a lot of experience and knowledge about buggy hardware. In
case it's a btrfs bug we'd be interested to know at least something that
could help to narrow it down.

d.