From: Jeff Moyer <jmoyer@redhat.com>
To: crimil tradalo <crimiltradalo@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Martin K. Petersen" <mkp@mkp.net>
Subject: Re: filesystem with integrity checking
Date: Wed, 13 May 2009 15:33:42 -0400 [thread overview]
Message-ID: <x49eiusu7ah.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <d978a99e0905131013p645317dfy2747b531e550ba9d@mail.gmail.com> (crimil tradalo's message of "Wed, 13 May 2009 13:13:58 -0400")
crimil tradalo <crimiltradalo@gmail.com> writes:
> I am looking for a filesystem that supports integrity checking of
> files with some kind of checksum/hash.
>
> For example, for each block an SHA hash is stored when written and
> verified when read. If the underlying hardware has corrupted the data,
> or returned a different block than expected, the filesystem can detect
> the error.
>
> Obviously, ideal would be integration with the RAID layer so that
> valid data could be found in the redundancy, similar to ZFS, but I
> don't expect this to exist.
>
> The last time I saw this discussed, the consensus seemed to be that it
> wasn't worth the CPU time. I hope that as CPUs have gotten faster and
> data sets larger, more people are noticing how frequent data
> corruption occurs and are beginning to respect the value of an OS
> ensuring the integrity of data on permanent storage. Everyone here
> must have experienced data corruption that is either seemingly-random
> or traced to bad hardware. I'd like to detect such corruption as soon
> as it happens, rather than after it has caused a catastrophic loss of
> data.
>
> If there is none that currently supports this, I am curious if any
> intend to support it eventually. I see it mentioned in BTRFS
> documentation, but considering the low odds of a new filesystem
> actually becoming viable, I'm more interested in a practical solution.
>
> My understanding is that the only filesystems that offer this are ZFS
> and WAFL, neither of which is going to be useful on Linux of course.
You may want to take a look at the DIF/DIX work that Martin K. Petersen
is doing:
http://oss.oracle.com/projects/data-integrity/
Cheers,
Jeff
prev parent reply other threads:[~2009-05-13 19:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 17:13 crimil tradalo
2009-05-13 19:33 ` Jeff Moyer [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=x49eiusu7ah.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=crimiltradalo@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mkp@mkp.net \
/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
all inboxes | Powered by JetHome®