From: Ted Ts'o <tytso@mit.edu>
To: James Bottomley <James.Bottomley@suse.de>
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 16:24:56 -0500 [thread overview]
Message-ID: <20110228212456.GI28617@thunk.org> (raw)
In-Reply-To: <1298928051.2487.50.camel@mulgrave.site>
On Mon, Feb 28, 2011 at 03:20:51PM -0600, James Bottomley wrote:
> 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.
I bet the manufacturers will say the drive works just fine --- as long
as you use the Windows drivers that they thoughtfully provided with
the HDD. :-)
- Ted
next prev parent reply other threads:[~2011-02-28 21:25 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
2011-02-28 21:24 ` Ted Ts'o [this message]
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=20110228212456.GI28617@thunk.org \
--to=tytso@mit.edu \
--cc=James.Bottomley@suse.de \
--cc=ibragimovrinat@mail.ru \
--cc=jmoyer@redhat.com \
--cc=linux-fsdevel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.