From: Neil Brown <neilb@suse.de>
To: CoolCold <coolthecold@gmail.com>
Cc: Philip Hands <phil@hands.com>, linux-raid@vger.kernel.org
Subject: Re: mdadm seems not be doing rewrites on unreadable blocks
Date: Tue, 30 Nov 2010 21:59:43 +1100 [thread overview]
Message-ID: <20101130215943.395a7622@notabene.brown> (raw)
In-Reply-To: <AANLkTin+k_xDs0gS+NWpzdyMe5Qy7_iCL9cHpX5RmUUB@mail.gmail.com>
On Tue, 30 Nov 2010 13:40:25 +0300 CoolCold <coolthecold@gmail.com> wrote:
> On Tue, Nov 30, 2010 at 3:52 AM, Neil Brown <neilb@suse.de> wrote:
> > When you write 512 byte blocks to a block device, it will read a 4096 byte
> > block, update the 512 bytes, and write the 4096 bytes back.
> >
> >
> >>
> >> Which gives rise to this:
> >>
> >> [325487.740650] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> >> [325487.740746] ata2.00: irq_stat 0x00060002, device error via D2H FIS
> >> [325487.740841] ata2.00: failed command: READ DMA
> >
> > Yep. read error while trying to pre-read the 4K block.
> Hmm, is true for any block device? i.e. if blockdev --getss reports
> sector size is 512 byte. Or this is related to page size?
>
PAGE_SIZE.
NeilBrown
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-11-30 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-29 15:23 mdadm seems not be doing rewrites on unreadable blocks Philip Hands
2010-11-30 0:52 ` Neil Brown
2010-11-30 10:40 ` CoolCold
2010-11-30 10:59 ` Neil Brown [this message]
2010-11-30 18:36 ` Philip Hands
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=20101130215943.395a7622@notabene.brown \
--to=neilb@suse.de \
--cc=coolthecold@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=phil@hands.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).