From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Benjamin LaHaise <ben@communityfibre.ca>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: linux-mm@kvack.org - limping on a backup
Date: Fri, 25 Jun 2021 10:00:15 -0700 [thread overview]
Message-ID: <214c41fae1f1b148e5b04a58c1b018fb091d7e83.camel@HansenPartnership.com> (raw)
In-Reply-To: <20210622145954.GA4058@kvack.org>
On Tue, 2021-06-22 at 10:59 -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. New hardware will be
> deployed this afternoon after an attempt at data recovery is made.
Perhaps it's time to move this list over to vger or the linux.dev
infrastructure now that it's being brought up? We already migrated the
containers list without too much pain.
Regards,
James
next prev parent reply other threads:[~2021-06-25 17:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 14:59 linux-mm@kvack.org - limping on a backup Benjamin LaHaise
2021-06-24 12:12 ` David Sterba
2021-06-25 17:00 ` James Bottomley [this message]
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=214c41fae1f1b148e5b04a58c1b018fb091d7e83.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--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;
as well as URLs for NNTP newsgroup(s).