From: Theodore Ts'o <tytso@mit.edu>
To: folkert <folkert@vanheusden.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: checksums
Date: Tue, 14 May 2013 09:18:30 -0400 [thread overview]
Message-ID: <20130514131830.GA19563@thunk.org> (raw)
In-Reply-To: <20130514091407.GC2041@belle.intranet.vanheusden.com>
On Tue, May 14, 2013 at 11:14:08AM +0200, folkert wrote:
>
> Is it possible to "scrub" (check/verify) (the new-) checksums in ext4?
When e2fsck does a full check, it verifies the contents of all of the
metadata blocks, and this includes verifying all of the checksums.
> Also: is it planned to add an option to add checksums to the data as
> well?
That's not currently on the development roadmap; I could imagine
someone deciding to design an extension to ext4 that would do this
probably by storing the checksums in the indirect blocks, but no one
is currently working on it.
Regards,
- Ted
next prev parent reply other threads:[~2013-05-14 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 9:14 checksums folkert
2013-05-14 13:18 ` Theodore Ts'o [this message]
2013-05-14 14:40 ` checksums folkert
2013-05-14 18:09 ` checksums Darrick J. Wong
2013-05-14 18:57 ` checksums folkert
2013-05-14 19:21 ` checksums Darrick J. Wong
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=20130514131830.GA19563@thunk.org \
--to=tytso@mit.edu \
--cc=folkert@vanheusden.com \
--cc=linux-ext4@vger.kernel.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).