From: "Theodore Ts'o" <tytso@mit.edu>
To: Chris Murphy <lists@colorremedies.com>
Cc: Qu Wenruo <quwenruo.btrfs@gmx.com>,
Nikolay Borisov <nborisov@suse.com>,
linux-block@vger.kernel.org, dm-devel@redhat.com,
Zdenek Kabelac <zkabelac@redhat.com>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [dm-devel] Ideas to reuse filesystem's checksum to enhance dm-raid1/10/5/6?
Date: Mon, 20 Nov 2017 21:53:29 -0500 [thread overview]
Message-ID: <20171121025329.ll72kg6yqkjeaz5o@thunk.org> (raw)
In-Reply-To: <CAJCQCtRUGEdu13RCKFb6uZQ3UCzoAByhu97FdwQoFPxvsOua0Q@mail.gmail.com>
On Thu, Nov 16, 2017 at 03:32:05PM -0700, Chris Murphy wrote:
>
> XFS by default does metadata csums. But ext4 doesn't use it for either
> metadata or the journal by default still, it is still optional. So for
> now it mainly benefits XFS.
Metadata checksums are enabled by default in the version of e2fsprogs
shipped by Debian. Since there were no real problems reported by
Debian users, in the next release of e2fsprogs, coming soon, it will
be enabled by default for all new ext4 file systems.
Regards,
- Ted
next prev parent reply other threads:[~2017-11-21 2:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 2:18 Ideas to reuse filesystem's checksum to enhance dm-raid1/10/5/6? Qu Wenruo
2017-11-16 6:54 ` Nikolay Borisov
2017-11-16 7:38 ` Qu Wenruo
2017-11-16 7:42 ` Nikolay Borisov
2017-11-16 8:08 ` Qu Wenruo
2017-11-16 9:43 ` Zdenek Kabelac
2017-11-16 10:04 ` Qu Wenruo
2017-11-16 12:33 ` Zdenek Kabelac
2017-11-16 12:41 ` Austin S. Hemmelgarn
2017-11-16 14:06 ` Qu Wenruo
2017-11-16 16:47 ` Austin S. Hemmelgarn
2017-11-16 21:05 ` Pasi Kärkkäinen
2017-11-17 1:30 ` Qu Wenruo
2017-11-17 12:22 ` Austin S. Hemmelgarn
2017-11-16 22:32 ` Chris Murphy
2017-11-17 1:22 ` Qu Wenruo
2017-11-17 1:54 ` Chris Murphy
2017-11-17 1:55 ` Chris Murphy
2017-11-21 2:53 ` Theodore Ts'o [this message]
2017-11-17 1:26 ` Andreas Dilger
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=20171121025329.ll72kg6yqkjeaz5o@thunk.org \
--to=tytso@mit.edu \
--cc=dm-devel@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=nborisov@suse.com \
--cc=quwenruo.btrfs@gmx.com \
--cc=zkabelac@redhat.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).