linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ric Wheeler <rwheeler@redhat.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Andreas Dilger <adilger@sun.com>,
	Eric Sandeen <sandeen@redhat.com>,
	ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH, RFC] mke2fs: get device topology values from blkid
Date: Tue, 22 Sep 2009 07:30:08 -0700	[thread overview]
Message-ID: <4AB8DF70.8000406@redhat.com> (raw)
In-Reply-To: <yq1skeh5oqf.fsf@sermon.lab.mkp.net>

On 09/20/2009 01:46 PM, Martin K. Petersen wrote:
>>>>>> "Andreas" == Andreas Dilger<adilger@sun.com>  writes:
>>>>>>              
> Andreas>  Yes, there is more chance that writing sector 7 (due to 4k
> Andreas>  sector r-m-w) will cause collateral damage, but the truth even
> Andreas>  today is that disks are not going to fail a single 512-byte
> Andreas>  sector at one time, but more likely 64kB (or whatever the
> Andreas>  remapping unit size is), so this isn't really introducing a new
> Andreas>  failure mode.
>
> I keep hearing this disk drive "internal block size" of 32KB or 64KB
> being mentioned.  And yet none of the drive firmware engineers I talk to
> on a regular basis have ever heard of such a thing...
>    

I have not heard of drives with that kind of internal block size for 
single drives.

What is common is that reads (often) are often done in much larger 
chunks like this (basically, if you are reading, it normally makes sense 
to read a whole track from the platter :-)

Array vendors definitely do have larger internal block sizes.

ric



  reply	other threads:[~2009-09-22 14:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17 22:22 [PATCH, RFC] mke2fs: get device topology values from blkid Eric Sandeen
2009-09-18  5:55 ` Andreas Dilger
2009-09-18 14:04   ` Eric Sandeen
2009-09-18 14:20     ` Andreas Dilger
2009-09-18 14:30       ` Eric Sandeen
2009-09-18 16:43       ` Theodore Tso
2009-09-18 16:57         ` Eric Sandeen
2009-09-18  6:13 ` Martin K. Petersen
2009-09-18 14:18   ` Andreas Dilger
2009-09-18 14:23   ` Eric Sandeen
2009-09-18 19:40     ` Martin K. Petersen
2009-09-18 20:28       ` Andreas Dilger
2009-09-20 20:46         ` Martin K. Petersen
2009-09-22 14:30           ` Ric Wheeler [this message]
2009-09-18 23:59 ` Karel Zak
2009-09-19  3:03   ` Eric Sandeen
2009-09-21 17:06 ` [PATCH V2] " Eric Sandeen
2009-10-02 16:32   ` [PATCH V3] " Eric Sandeen
2009-10-04 19:16     ` Theodore Tso

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=4AB8DF70.8000406@redhat.com \
    --to=rwheeler@redhat.com \
    --cc=adilger@sun.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=sandeen@redhat.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).