From: tytso@mit.edu
To: Ric Wheeler <rwheeler@redhat.com>
Cc: Anton Altaparmakov <aia21@cam.ac.uk>,
Nick Piggin <npiggin@suse.de>, Dave Chinner <david@fromorbit.com>,
Jan Kara <jack@suse.cz>,
Hidehiro Kawai <hidehiro.kawai.ez@hitachi.com>,
linux-kernel@vger.kernel.org, linux-ext4@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Andreas Dilger <adilger@sun.com>,
Satoshi OSHIMA <satoshi.oshima.fk@hitachi.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: IO error semantics
Date: Mon, 25 Jan 2010 12:47:23 -0500 [thread overview]
Message-ID: <20100125174723.GB28459@thunk.org> (raw)
In-Reply-To: <4B5DB78D.2090408@redhat.com>
On Mon, Jan 25, 2010 at 10:23:57AM -0500, Ric Wheeler wrote:
>
> For permanent write errors, I would expect any modern drive to do a
> sector remapping internally. We should never need to track this kind
> of information for any modern device that I know of (S-ATA, SAS,
> SSD's and raid arrays should all handle this).
... and if the device is run out of all of its blocks in its spare
blocks pool, it's probably well past the time to replace said disk.
BTW, I really liked Dave Chinner's summary of the issues involved; I
ran into Kawai-san last week at Linux.conf.au, and we discussed pretty
much the same thing over lunch. (i.e., that it's a hard problem, and
in some cases we need to retry the writes, such as a transient FC path
problem --- but some kind of write throttling is critical or we could
end up choking the VM due to too many pages getting dirtied and no way
of cleaning them.)
- Ted
next prev parent reply other threads:[~2010-01-25 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B4EB5B9.4020809@hitachi.com>
[not found] ` <4B4EDE5C.8040600@hitachi.com>
[not found] ` <4B4EEE86.7080807@hitachi.com>
[not found] ` <20100114141803.GB3146@quack.suse.cz>
2010-01-18 5:18 ` [PATCH] ext3: prevent reread after write IO error v2 Nick Piggin
2010-01-18 6:05 ` IO error semantics Nick Piggin
2010-01-18 12:24 ` Dave Chinner
2010-01-18 14:00 ` Nick Piggin
2010-01-18 22:51 ` Dave Chinner
2010-01-18 23:33 ` Anton Altaparmakov
2010-01-25 15:23 ` Ric Wheeler
2010-01-25 16:15 ` Greg Freemyer
2010-01-25 17:47 ` tytso [this message]
2010-01-25 17:50 ` Ric Wheeler
2010-01-25 17:55 ` Nick Piggin
[not found] ` <4B5DD9DB.7070300@redhat.com>
2010-01-25 17:59 ` Nick Piggin
[not found] ` <20100125175529.GB2018@laptop>
2010-01-26 6:19 ` Dave Chinner
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=20100125174723.GB28459@thunk.org \
--to=tytso@mit.edu \
--cc=adilger@sun.com \
--cc=aia21@cam.ac.uk \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=rwheeler@redhat.com \
--cc=satoshi.oshima.fk@hitachi.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).