From: Stefan Behrens <sbehrens@giantdisaster.de>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-btrfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 0/3] Btrfs: add IO error device stats
Date: Fri, 25 May 2012 19:49:47 +0200 [thread overview]
Message-ID: <4FBFC63B.6050403@giantdisaster.de> (raw)
In-Reply-To: <20120525151854.GA23362@infradead.org>
It would be helpful if already the generic block layer would offer
device error counters. Then btrfs could read them, add own counters for
its checksum detected errors, and store everything persistently in the
filesystem.
The goal is to replace disks that have an increased error rate with
spare disks, and the goal is to repair this degenerated RAID state quickly.
On 05/25/2012 17:18, Christoph Hellwig wrote:
> Can you explain why the device error counters should be in a filesystem
> instead of generic block layer code?
>
> On Fri, May 25, 2012 at 04:06:07PM +0200, Stefan Behrens wrote:
[...]
>> The goal is to detect when drives start to get an increased error rate,
>> when drives should be replaced soon. Therefore statistic counters are
>> added that count IO errors (read, write and flush). Additionally, the
>> software detected errors like checksum errors and corrupted blocks are
>> counted.
>>
>> An ioctl interface is added to get the device statistic counters.
>> A second ioctl is added to atomically get and reset these counters.
>>
>> The device statistics are written into the device tree with each
>> transaction commit. Only modified statistics are written.
>> When a filesystem is mounted, the device statistics for each involved
>> device are read from the device tree and used to initialize the
>> counters.
>>
>> A patch for the btrfs-progs world will also be sent.
>>
>> Stefan Behrens (3):
>> Btrfs: add device counters for detected IO and checksum errors
>> Btrfs: add ioctl to get and reset the device stats
>> Btrfs: read device stats on mount, write modified ones during commit
>>
>> fs/btrfs/ctree.h | 38 ++++++
>> fs/btrfs/disk-io.c | 20 +++-
>> fs/btrfs/extent_io.c | 18 ++-
>> fs/btrfs/ioctl.c | 26 +++++
>> fs/btrfs/ioctl.h | 33 ++++++
>> fs/btrfs/print-tree.c | 3 +
>> fs/btrfs/scrub.c | 65 ++++++++---
>> fs/btrfs/transaction.c | 4 +
>> fs/btrfs/volumes.c | 304 +++++++++++++++++++++++++++++++++++++++++++++++-
>> fs/btrfs/volumes.h | 52 +++++++++
>> 10 files changed, 539 insertions(+), 24 deletions(-)
>>
>> --
>> 1.7.10.2
next prev parent reply other threads:[~2012-05-25 17:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 14:06 [PATCH v5 0/3] Btrfs: add IO error device stats Stefan Behrens
2012-05-25 14:06 ` [PATCH v5 1/3] Btrfs: add device counters for detected IO and checksum errors Stefan Behrens
2012-05-25 14:06 ` [PATCH v5 2/3] Btrfs: add ioctl to get and reset the device stats Stefan Behrens
2012-05-25 14:06 ` [PATCH v5 3/3] Btrfs: read device stats on mount, write modified ones during commit Stefan Behrens
2012-05-25 15:18 ` [PATCH v5 0/3] Btrfs: add IO error device stats Christoph Hellwig
2012-05-25 17:49 ` Stefan Behrens [this message]
2012-05-25 20:41 ` Arne Jansen
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=4FBFC63B.6050403@giantdisaster.de \
--to=sbehrens@giantdisaster.de \
--cc=hch@infradead.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).