From: Neil Brown <neilb@suse.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Justin Piszcz <jpiszcz@lucidpixels.com>, linux-raid@vger.kernel.org
Subject: Re: Linux Software RAID Bitmap Question
Date: Wed, 28 Feb 2007 08:04:15 +1100 [thread overview]
Message-ID: <17892.40143.389564.172608@notabene.brown> (raw)
In-Reply-To: message from Bill Davidsen on Tuesday February 27
On Tuesday February 27, davidsen@tmr.com wrote:
> Neil Brown wrote:
> > When md find a bad block (read failure) it either fixes it (by
> > successfully over-writing the correct date) or fails the drive.
> >
> > The count of the times that this has happened is available via
> > /sys/block/mdX/md/errors
> >
> What kernel provides this? I have system running everything from 2.6.15
> to 2.6.20-get14, and there is no such file in any of them. There is a
> per-device errors file one level down, but that presumably wouldn't be
> in the superblock.
Sorry, I did get that wrong. As you say it is a per-device field:
/sys/block/mdX/md/dev-*/errors
which makes sense because it is individual devices that get errors,
not whole arrays. And it *is* stored in the superblock for v1. The
superblock has a per-device section which is potentially different on
each device, The corrected-error count is stored there.
>
> Do I have to go from 0.90 to v1 or later superblocks to get this, and if
> so is that a safe thing to do?
It is not currently easy to convert a v0.90 array to use v1
superblocks. I should put that on my todo list as it isn't
conceptually hard.
NeilBrown
next prev parent reply other threads:[~2007-02-27 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-25 14:05 Linux Software RAID Bitmap Question Justin Piszcz
2007-02-26 4:22 ` Neil Brown
2007-02-27 17:42 ` Bill Davidsen
2007-02-27 21:04 ` Neil Brown [this message]
2007-02-28 3:00 ` Bill Davidsen
2007-02-28 19:30 ` dean gaudet
2007-02-28 19:44 ` Justin Piszcz
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=17892.40143.389564.172608@notabene.brown \
--to=neilb@suse.de \
--cc=davidsen@tmr.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-raid@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).