From: Tomasz Chmielewski <tch@virtall.com>
To: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Cc: srb@cuci.nl
Subject: Re: Kernel traces
Date: Wed, 12 Dec 2018 00:21:05 +0900 [thread overview]
Message-ID: <17869db912a3d4ec0bfb523a3ac9d132@virtall.com> (raw)
> (The most recent ones are from v4.19.7):
Please, don't run 4.19.x lower than v4.19.8. It will likely eat your
filesystem.
Reference:
https://www.phoronix.com/scan.php?page=news_item&px=Linux-4.19.8-Released
With btrfs, the chances are that data and metadata checksumming will
detect the introduced corruption and fix the error, but still, it's not
safe (especially if you don't have btrfs RAID i.e. on other partitions).
Tomasz Chmielewski
https://lxadm.com
next reply other threads:[~2018-12-11 15:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 15:21 Tomasz Chmielewski [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-12-10 12:05 Kernel traces Stephen R. van den Berg
2018-12-10 16:54 ` Chris Murphy
2018-12-11 11:52 ` Stephen R. van den Berg
2018-12-12 6:16 ` Chris Murphy
2018-12-12 7:26 ` Stephen R. van den Berg
2018-12-12 21:01 ` Chris Murphy
2018-12-28 9:20 ` Stephen R. van den Berg
2018-12-28 10:10 ` Qu Wenruo
2018-12-28 13:40 ` Stephen R. van den Berg
2018-12-28 13:46 ` Qu Wenruo
2018-12-28 15:00 ` Stephen R. van den Berg
2019-01-23 15:50 ` Stephen R. van den Berg
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=17869db912a3d4ec0bfb523a3ac9d132@virtall.com \
--to=tch@virtall.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=srb@cuci.nl \
/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).