From: Andrea Gelmini <andrea.gelmini@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Zygo Blaxell <ce3g8jdj@umail.furryterror.org>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: btrfs vs write caching firmware bugs (was: Re: BTRFS recovery not possible)
Date: Tue, 2 Jul 2019 15:32:19 +0200 [thread overview]
Message-ID: <20190702133219.GA24228@glet> (raw)
In-Reply-To: <CAJCQCtRrT5pUxOxfKWTC=zt9E=ZxRaiLeBxngqc6YVQEYp8n_g@mail.gmail.com>
On Mon, Jun 24, 2019 at 11:31:35AM -0600, Chris Murphy wrote:
> Right. The questions I have: should Btrfs (or any file system) be able
> to detect such devices and still protect the data? i.e. for the file
I have more than 600 industrial machine all around the world.
After a few fs corruption (ext4) I found the culprit in the SSD
(choosed by the provider) cheating about flush/sync.
Well, forcing the data=journal at mount, fixed the problem. Same SSDs,
since years, no more problem at all.
Personally I don't really care about performance. Resilience first.
Than options to fix even if the hardware is in the middle of nowhere,
without need to go on site.
Thanks a lot for your work,
Andrea
next prev parent reply other threads:[~2019-07-02 13:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 20:45 btrfs vs write caching firmware bugs (was: Re: BTRFS recovery not possible) Zygo Blaxell
2019-06-24 0:46 ` Qu Wenruo
2019-06-24 4:29 ` Zygo Blaxell
2019-06-24 5:39 ` Qu Wenruo
2019-06-24 17:31 ` Chris Murphy
2019-06-26 2:30 ` Zygo Blaxell
2019-07-02 13:32 ` Andrea Gelmini [this message]
2019-06-24 2:45 ` Remi Gauvin
2019-06-24 4:37 ` Zygo Blaxell
2019-06-24 5:27 ` Zygo Blaxell
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=20190702133219.GA24228@glet \
--to=andrea.gelmini@gmail.com \
--cc=ce3g8jdj@umail.furryterror.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=quwenruo.btrfs@gmx.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).