From: Greg Freemyer <greg.freemyer@gmail.com>
To: David Rees <drees76@gmail.com>
Cc: Iain Rauch <groups@email.iain.rauch.co.uk>,
st0ff@npl.de, linux-raid@vger.kernel.org
Subject: Re: How to fix Current_Pending_Sector?
Date: Thu, 18 Mar 2010 17:47:13 -0400 [thread overview]
Message-ID: <87f94c371003181447w2147cb87h41d8b16613ee1471@mail.gmail.com> (raw)
In-Reply-To: <72dbd3151003181237v6ebf87b7i4ec9563f6bfde758@mail.gmail.com>
On Thu, Mar 18, 2010 at 3:37 PM, David Rees <drees76@gmail.com> wrote:
> On Mon, Mar 15, 2010 at 4:20 AM, Iain Rauch
> <groups@email.iain.rauch.co.uk> wrote:
>> The 'Current_Pending_Sector' was still 1, so I dd zero onto the whole drive.
>> I guess I could have just done part of it, but I suppose that verified the
>> whole drive 'works'. It only took ~5 hours. Funnily enough this did fix the
>> Current_pending_sectors count back to zero. Still no error reports in the
>> SMART data, and 'Reallocated_Event_Count' didn't go up - shouldn't that have
>> gone up to one?
>
> No - the drive was able to successfully write to the sector it was
> unable to read from. If the write had failed, it would have
> reallocated the sector.
>
> -Dave
Dave,
Most sector writes are blind (ie. non-verified).
Is your theory that if the sector is marked as a Pending_Bad_Sector a
write is done, but it is verified, and a reallocate only occurs if the
verify fails?
I've never heard that theory, but it makes great sense.
Greg
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-18 21:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 11:51 How to fix Current_Pending_Sector? Iain Rauch
2010-03-11 12:06 ` Michael Evans
2010-03-11 12:25 ` Iain Rauch
2010-03-11 16:54 ` Stefan /*St0fF*/ Hübner
2010-03-15 11:20 ` Iain Rauch
2010-03-18 17:35 ` CoolCold
2010-03-18 19:37 ` David Rees
2010-03-18 21:47 ` Greg Freemyer [this message]
2010-03-19 7:22 ` Stefan /*St0fF*/ Hübner
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=87f94c371003181447w2147cb87h41d8b16613ee1471@mail.gmail.com \
--to=greg.freemyer@gmail.com \
--cc=drees76@gmail.com \
--cc=groups@email.iain.rauch.co.uk \
--cc=linux-raid@vger.kernel.org \
--cc=st0ff@npl.de \
/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