From: Andrei Borzenkov <arvidjaar@gmail.com>
To: Timothy Pearson <tpearson@raptorengineering.com>,
Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Unusual crash -- data rolled back ~2 weeks?
Date: Sun, 10 Nov 2019 11:04:00 +0300 [thread overview]
Message-ID: <08aced90-6dac-646a-a3c3-445eaf1e9fbb@gmail.com> (raw)
In-Reply-To: <1503948411.128656.1573370293214.JavaMail.zimbra@raptorengineeringinc.com>
10.11.2019 10:18, Timothy Pearson пишет:
>>>
>>> Do the described symptoms (what little we know of them at this point) line up
>>> with the issues fixed by https://patchwork.kernel.org/patch/11141559/ ? Right
>>> now we're hoping that this particular issue was fixed by that series, but if
>>> not we might consider increasing backup frequency to nightly for this
>>> particular array and seeing if it happens again.
>>
>> That fix is already in v5.3, thus I don't think that's the case.
>>
>> Thanks,
>> Qu
>
> Looking more carefully, the server in question had been booted on 5.3-rc3 somehow. It's possible that this was because earlier versions were showing driver problems with the other hardware, but somehow this machine was running 5.3-rc3 and the patch was created *after* rc3 release.
The patch apparently was added in 5.3 final so way after rc3.
prev parent reply other threads:[~2019-11-10 8:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-09 22:33 Unusual crash -- data rolled back ~2 weeks? Timothy Pearson
2019-11-09 22:48 ` Timothy Pearson
2019-11-10 3:38 ` Qu Wenruo
2019-11-10 6:47 ` Timothy Pearson
2019-11-10 6:54 ` Qu Wenruo
2019-11-10 7:18 ` Timothy Pearson
2019-11-10 7:45 ` Qu Wenruo
2019-11-10 7:48 ` Timothy Pearson
2019-11-10 10:02 ` Timothy Pearson
2019-11-10 20:10 ` Zygo Blaxell
2019-11-11 23:28 ` Timothy Pearson
2019-11-11 23:33 ` Timothy Pearson
2019-11-12 11:30 ` Chris Murphy
2019-11-10 8:04 ` Andrei Borzenkov [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=08aced90-6dac-646a-a3c3-445eaf1e9fbb@gmail.com \
--to=arvidjaar@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=tpearson@raptorengineering.com \
/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).