linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@suse.de>
To: Ted Ts'o <tytso@mit.edu>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
	Jeff Moyer <jmoyer@redhat.com>,
	Ibragimov Rinat <ibragimovrinat@mail.ru>,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH][RFC]ext4 on 4k-sector drives without read-modify-write support
Date: Mon, 28 Feb 2011 15:20:51 -0600	[thread overview]
Message-ID: <1298928051.2487.50.camel@mulgrave.site> (raw)
In-Reply-To: <20110228210541.GF28617@thunk.org>

On Mon, 2011-02-28 at 16:05 -0500, Ted Ts'o wrote:
> On Mon, Feb 28, 2011 at 03:19:21PM -0500, Martin K. Petersen wrote:
> > Kind of, yes. But that involves teaching every ATA driver in $LEGACY_OS
> > about 4KB logical blocks. There is little value is switching to 4KB
> > logical blocks in the first place. So the claim is that it is easier to
> > stick with 512-byte addressing, leave the I/O stack intact, and require
> > the filesystem to always issue aligned units of 4KB.
> > 
> > That saves the drive vendors from implementing RMW logic and puts the
> > burden on us. Perfect deal.
> 
> So it there a reliable way to detect that disk drives that don't have
> the Read-Modify-Write logic?  If that can be reflected up the I/O
> layer I can have mke2fs enforce that restriction, which currently we
> only enforce if the logical blocksize is 4k.

Well, we could blacklist it to force the logical block size up to 4k
based on identification by the inquiry strings (that, of course,
involves finding all the inquiry strings).  It's just that we're
practically out of blacklist bits ... it's just I thought we'd finally
got all manufacturers on the same page as standards compliance ... doing
something like this would send us back to the dark ages again.

Could we just have a campaign to send drives that fail like this back?
That might actually get the message across to the manufacturers .. and
it could arguably be covered under the warranty.

James



  parent reply	other threads:[~2011-02-28 21:20 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-26 18:24 [PATCH][RFC]ext4 on 4k-sector drives without read-modify-write support Ibragimov Rinat
2011-02-28 14:52 ` Jeff Moyer
2011-02-28 14:58   ` Martin K. Petersen
2011-02-28 18:09     ` Ted Ts'o
2011-02-28 20:19       ` Martin K. Petersen
2011-02-28 21:05         ` Ted Ts'o
2011-02-28 21:10           ` Jeff Moyer
2011-02-28 21:22             ` Ted Ts'o
2011-02-28 21:57               ` Jeff Moyer
2011-03-01 15:19                 ` Martin K. Petersen
2011-02-28 21:20           ` James Bottomley [this message]
2011-02-28 21:24             ` Ted Ts'o
2011-02-28 21:23           ` Martin K. Petersen
2011-02-28 22:52       ` [PATCH][RFC]ext4 on 4k-sector drives without read-modify-writesupport Ibragimov Rinat
2011-03-01 22:16       ` Ibragimov Rinat
2011-03-10 17:01         ` Ibragimov Rinat
2011-02-28 17:54   ` [PATCH][RFC]ext4 on 4k-sector drives without read-modify-write support Ibragimov Rinat
2012-09-27 11:41     ` Mike

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=1298928051.2487.50.camel@mulgrave.site \
    --to=james.bottomley@suse.de \
    --cc=ibragimovrinat@mail.ru \
    --cc=jmoyer@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=tytso@mit.edu \
    /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).