From: Sarah Newman <srn@prgmr.com>
To: linux-raid@vger.kernel.org
Subject: Bogus entry in mdadm bad blocks list and question about particular commit
Date: Tue, 2 Feb 2016 12:34:59 -0800 [thread overview]
Message-ID: <56B112F3.9010609@prgmr.com> (raw)
I added some more drives to a raid 1 last night where some devices had existing bad block entries. There was nothing of particular interest in
/var/log/messages. Afterwards there is:
$ sudo /sbin/mdadm --examine-badblocks /dev/sdl1
Bad-blocks on /dev/sdl1:
11986270392325491 for 51 sectors
The total number of sectors on the drive is 3907029168.
The start sector in the bad blocks list is 2a95730cea9573 in hex, I don't know if that string has any special significance or not.
$ sudo /sbin/mdadm --examine /dev/sdl1
/dev/sdl1:
Magic : a92b4efc
Version : 1.0
Feature Map : 0x8
Raid Level : raid1
Raid Devices : 11
Avail Dev Size : 20971368 (10.00 GiB 10.74 GB)
Array Size : 10485632 (10.00 GiB 10.74 GB)
Used Dev Size : 20971264 (10.00 GiB 10.74 GB)
Super Offset : 20971504 sectors
Unused Space : before=0 sectors, after=232 sectors
State : clean
Update Time : Tue Feb 2 10:50:33 2016
Bad Block Log : 512 entries available at offset -8 sectors - bad blocks present.
Checksum : 4092aabf - correct
Events : 143560
Device Role : Active device 9
Array State : AAAAAAAAAAA ('A' == active, '.' == missing, 'R' == replacing)
The kernel is built from the Xen4CentOS 3.18.21-17 kernel, but there are no changes related to md in the code.
I looked for differences in between 3.18.21 and stable 3.18.y and the only interesting thing looked like e9206476ace "md/raid1: submit_bio_wait()
returns 0 on success". I don't think that's a smoking gun for the bogus bad blocks entry. But without that commit, mdadm with bad blocks enabled is
completely broken if there are write errors such that successful writes are reported as errors and vice versa, is that correct?
Thanks, Sarah
next reply other threads:[~2016-02-02 20:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 20:34 Sarah Newman [this message]
2016-02-02 20:46 ` Bogus entry in mdadm bad blocks list and question about particular commit Jes Sorensen
2016-02-02 21:09 ` Sarah Newman
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=56B112F3.9010609@prgmr.com \
--to=srn@prgmr.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 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.