From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Neil Brown <neilb@suse.de>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
jens.axboe@oracle.com, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: [PATCH] md: Add support for data integrity to MD
Date: Mon, 29 Sep 2008 10:51:54 -0400 [thread overview]
Message-ID: <yq1ej33f1it.fsf@sermon.lab.mkp.net> (raw)
In-Reply-To: <18649.43504.157272.351801@notabene.brown> (Neil Brown's message of "Wed\, 24 Sep 2008 12\:46\:08 +1000")
>>>>> "Neil" == Neil Brown <neilb@suse.de> writes:
Neil> But what if we subsequently add a different device to that array
Neil> which uses a different protection format. Would we be able to
Neil> tell the filesystem that integrity protection isn't available
Neil> any more? Or can we detect if the filesystem is using integrity
Neil> protection, and reject the new device if it doesn't match?
Generally the filesystem will look at the block device's integrity
profile every time it prepares an I/O. So if we add a subdevice and
detect a mismatch the mddev integrity profile should be removed.
Neil> In either case, some extra handling is needed in
Neil> bind_rdev_to_array.
This code has been sitting in my patch queue for several months
waiting for the core of the integrity stuff to go in. So I'm a bit
fuzzy on the details. I'll take a look...
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2008-09-29 14:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 0:18 [PATCH] md: Add support for data integrity to MD Martin K. Petersen
2008-09-21 0:26 ` Dan Williams
2008-09-21 2:01 ` Martin K. Petersen
2008-09-21 0:28 ` Stable versions of mdadm berk walker
2008-09-21 1:07 ` Bill Davidsen
2008-09-21 1:24 ` berk walker
2008-09-24 2:46 ` [PATCH] md: Add support for data integrity to MD Neil Brown
2008-09-29 14:51 ` Martin K. Petersen [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=yq1ej33f1it.fsf@sermon.lab.mkp.net \
--to=martin.petersen@oracle.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).