From: Chris Murphy <lists@colorremedies.com>
To: scar <scar@drigon.com>
Cc: Linux-RAID <linux-raid@vger.kernel.org>
Subject: Re: moving spares into group and checking spares
Date: Wed, 14 Sep 2016 21:51:30 -0600 [thread overview]
Message-ID: <CAJCQCtRW9REafzmyk+W6aVxqxMUWCdXNkrST1e7udrH-zp26Uw@mail.gmail.com> (raw)
In-Reply-To: <nrd5ak$e8c$1@blaine.gmane.org>
On Wed, Sep 14, 2016 at 9:42 PM, scar <scar@drigon.com> wrote:
> 00 80 00
> Sep 12 08:05:34 hind kernel: [1350051.023847] end_request: critical medium
> error, dev sdk, sector 598457896
> Sep 12 08:05:35 hind kernel: [1350051.385810] md/raid:md0: read error
> corrected (8 sectors at 598455848 on sdk1)
> Sep 12 08:05:35 hind kernel: [1350051.385826] md/raid:md0: read error
> corrected (8 sectors at 598455856 on sdk1)
> Sep 12 08:05:35 hind kernel: [1350051.385834] md/raid:md0: read error
> corrected (8 sectors at 598455864 on sdk1)
> Sep 12 08:05:35 hind kernel: [1350051.385840] md/raid:md0: read error
> corrected (8 sectors at 598455872 on sdk1)
> Sep 12 08:05:35 hind kernel: [1350051.385847] md/raid:md0: read error
> corrected (8 sectors at 598455880 on sdk1)
> Sep 12 08:05:35 hind kernel: [1350051.385853] md/raid:md0: read error
> corrected (8 sectors at 598455888 on sdk1)
> Sep 12 08:05:35 hind kernel: [1350051.385859] md/raid:md0: read error
> corrected (8 sectors at 598455896 on sdk1)
> Sep 12 08:05:35 hind kernel: [1350051.385865] md/raid:md0: read error
> corrected (8 sectors at 598455904 on sdk1)
> Sep 12 08:05:35 hind kernel: [1350051.385873] md/raid:md0: read error
> corrected (8 sectors at 598455912 on sdk1)
> Sep 12 08:05:35 hind kernel: [1350051.385880] md/raid:md0: read error
> corrected (8 sectors at 598455920 on sdk1)
> Sep 12 13:39:43 hind kernel: [1370087.022160] md: md0: data-check done.
>
>
> so it seems to be working? although the sector reported by libata is
> different than what md corrected
Looks like it replaced the entire chunk that includes the bad sector.
Is the chunk size 32KiB?
--
Chris Murphy
next prev parent reply other threads:[~2016-09-15 3:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 5:18 moving spares into group and checking spares scar
2016-09-14 9:29 ` Andreas Klauer
[not found] ` <20160914092959.GA3584-oubN3LzF/wf25t9ic+4fgA@public.gmane.org>
2016-09-14 17:52 ` scar
2016-09-14 18:22 ` Roman Mamedov
2016-09-14 21:05 ` scar
2016-09-14 22:33 ` Chris Murphy
[not found] ` <CAJCQCtQJwOTYsWubd0rV-6PRL4kmVRKLfLr3=7ZPr1Zb3SrwtQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-14 22:59 ` scar
2016-09-14 23:15 ` Chris Murphy
[not found] ` <CAJCQCtQ1GHdQtShbW3U1o-fmXhT3fHrC7S9BxsxrrOG=0H_p3A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-15 3:42 ` scar
2016-09-15 3:51 ` Chris Murphy [this message]
[not found] ` <CAJCQCtRW9REafzmyk+W6aVxqxMUWCdXNkrST1e7udrH-zp26Uw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-09-28 0:19 ` scar
2016-09-29 1:17 ` NeilBrown
2016-09-14 18:35 ` Wols Lists
2016-09-29 1:21 ` NeilBrown
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=CAJCQCtRW9REafzmyk+W6aVxqxMUWCdXNkrST1e7udrH-zp26Uw@mail.gmail.com \
--to=lists@colorremedies.com \
--cc=linux-raid@vger.kernel.org \
--cc=scar@drigon.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.