From: Joe Peterson <lavajoe@gentoo.org>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Thomas King <kingttx@tomslinux.homelinux.org>,
linux-btrfs@vger.kernel.org
Subject: Re: Future Linux filesystems
Date: Tue, 03 Jun 2008 10:46:15 -0600 [thread overview]
Message-ID: <48457557.30000@gentoo.org> (raw)
In-Reply-To: <yq1ve0qo64o.fsf@sermon.lab.mkp.net>
Martin K. Petersen wrote:
> We're very concerned about data integrity. With btrfs everything is
> checksummed at the logical level. This allows you to detect data
> corruption, repair bad blocks using redundant, good copies, perform
> data scrubbing, etc.
That's the main reason I am interesting in btrfs, actually. :)
> A related, but orthogonal data integrity measure is the T10 DIF
> infrastructure that I am working on. DIF enables protection at the
> sector level and includes stuff like a data checksum and a locality
> check which ensures that the sector ends up the right place on disk.
Great! Really great to hear that this issue is being actively worked.
> Right now the DIF checksum is added at the block layer level. Work is
> in progress to move it up into the filesystems and from there into
> user space. Eventually we'd like to be able to generate the checksum
> in the application and pass it along the I/O path all the way out to
> the physical disk.
Yep, end-to-end is a great idea. Kudos to this and to btrfs!
-Joe
next prev parent reply other threads:[~2008-06-03 16:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 21:46 Future Linux filesystems Thomas King
[not found] ` <20080603065205.GA19533@infradead.org>
2008-06-03 14:37 ` Thomas King
2008-06-03 15:02 ` Joe Peterson
2008-06-03 16:06 ` Martin K. Petersen
2008-06-03 16:46 ` Joe Peterson [this message]
2008-06-03 15:52 ` Evgeniy Polyakov
2008-06-03 16:17 ` Miguel Sousa Filipe
2008-06-04 2:14 ` Chris Mason
2008-06-04 14:00 ` Thomas King
2008-06-04 2:34 ` Dongjun Shin
-- strict thread matches above, loose matches on Subject: below --
2008-06-11 9:38 Tomasz Chmielewski
2008-06-11 16:27 ` Zach Brown
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=48457557.30000@gentoo.org \
--to=lavajoe@gentoo.org \
--cc=kingttx@tomslinux.homelinux.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=martin.petersen@oracle.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