Re: mdadm seems not be doing rewrites on unreadable blocks

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 30 Nov 2010 13:40:25 +0300 CoolCold <coolthecold@xxxxxxxxx> wrote:

> On Tue, Nov 30, 2010 at 3:52 AM, Neil Brown <neilb@xxxxxxx> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux