linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "NeilBrown" <neilb@suse.de>
Cc: John Robinson <john.robinson@anonymous.org.uk>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-raid@vger.kernel.org
Subject: Re: RFC: detection of silent corruption via ATA long sector reads
Date: Mon, 5 Jan 2009 14:24:35 +1100 (EST)	[thread overview]
Message-ID: <ac115cdd9ea4fb28aaec2453b57697b0.squirrel@neil.brown.name> (raw)
In-Reply-To: <yq1zli631yj.fsf@sermon.lab.mkp.net>

On Mon, January 5, 2009 1:45 pm, Martin K. Petersen wrote:
>>>>>> "John" == John Robinson <john.robinson@anonymous.org.uk> writes:
>
> John> Essentially DIF on 32k blocks instead of 512 byte ones. But
> John> perhaps this is a bad assumption and MD/DM already optimises out
> John> whole-chunk reads and writes where they're not required (for very
> John> short, less-than-one-chunk transactions), and I've no idea whether
> John> this happens a lot.
>
> I haven't looked at the RAID4/5/6 code for a long time so I'm not sure
> whether they only write dirty pages or the whole chunk + parity ditto.
> Neil?

md/RAID456 writes whole pages (aligned to the array) but not whole chunks.

If a filesystem request to write one page which is at a sector address
which is not a multiple of the page size, we will pre-read the read of
the two array-aligned pages, and when write them (and parity) back out.

Otherwise, it will just write the requested pages plus parity updates.

NeilBrown



  reply	other threads:[~2009-01-05  3:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.8mwKV7y4hm+Q6mvIKtp9QGoJYUU@ifi.uio.no>
     [not found] ` <fa.4QcsYZC0gJJwJ0eUOht3hDYaVWs@ifi.uio.no>
2008-12-28 22:40   ` RFC: detection of silent corruption via ATA long sector reads Sitsofe Wheeler
2008-12-30 13:48     ` Mark Lord
2009-01-02 20:26     ` Greg Freemyer
2009-01-02 20:43       ` Sitsofe Wheeler
2009-01-02 21:05         ` Greg Freemyer
2009-01-02 22:04       ` Martin K. Petersen
2009-01-02 22:41         ` Greg Freemyer
2009-01-03  3:01           ` Martin K. Petersen
2009-01-03 13:20         ` John Robinson
2009-01-04  7:37           ` Martin K. Petersen
2009-01-04 12:31             ` John Robinson
2009-01-04 13:49               ` John Robinson
2009-01-05  2:43                 ` Martin K. Petersen
2009-01-05  2:45               ` Martin K. Petersen
2009-01-05  3:24                 ` NeilBrown [this message]
2008-12-26 21:44 Greg Freemyer
2008-12-26 22:15 ` Robert Hancock
2008-12-28 22:26 ` Mark Lord

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=ac115cdd9ea4fb28aaec2453b57697b0.squirrel@neil.brown.name \
    --to=neilb@suse.de \
    --cc=john.robinson@anonymous.org.uk \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).