linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
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
Date: Thu, 24 Jun 2021 14:12:56 +0200	[thread overview]
Message-ID: <20210624121256.GS28158@twin.jikos.cz> (raw)
In-Reply-To: <20210622145954.GA4058@kvack.org>

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.


  reply	other threads:[~2021-06-24 12:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-22 14:59 Benjamin LaHaise
2021-06-24 12:12 ` David Sterba [this message]
2021-06-25 17:00 ` James Bottomley
2021-06-25 17:12   ` Benjamin LaHaise
2021-06-25 19:21     ` James Bottomley
2021-06-25 19:26       ` Benjamin LaHaise
2021-06-25 21:52         ` James Bottomley
2021-06-28 13:46         ` Jason Gunthorpe
2021-06-28 13:53           ` Benjamin LaHaise
2021-06-28 14:26             ` Jason Gunthorpe
2021-06-28 14:40               ` Benjamin LaHaise
2021-06-28 16:20                 ` Jason Gunthorpe

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=20210624121256.GS28158@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=ben@communityfibre.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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