From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: linux-raid@vger.kernel.org
Subject: I/O errors without erros from underlying device
Date: Mon, 7 Dec 2015 17:05:26 +0100 [thread overview]
Message-ID: <201512071705.27177.a.miskiewicz@gmail.com> (raw)
Hi.
4.3.0 kernel, raid6 array:
md7 : active raid6 sdg[10] sdad1[9] sdac1[8] sdag1[7] sdaf1[6] sdae1[5] sdaj1[4] sdai1[3] sdah1[2] sdn1[1]
31255089152 blocks super 1.2 level 6, 512k chunk, algorithm 2 [10/10] [UUUUUUUUUU]
bitmap: 1/30 pages [4KB], 65536KB chunk
array had weird failure where many disks went into failed state but
remove && adding these disks "fixed" it (turns out not really fixed it).
Unfortunately now some reads fail:
pread(4, 0x1483a00, 4096, 16003680464896) = -1 EIO (Input/output error)
To reproduce used xfs_io
xfs_io -d -c "pread 16003680464896 4096" /dev/md7
pread64: Input/output error
which does pread exactly as shown above.
write also fails for that area:
xfs_io -d -c "pwrite 16003680464896 4096" /dev/md7
pwrite64: Input/output error
Note that nothing is written in dmesg when that happens.
I've tried various offsets and sizes of pread and at some point that was logged:
[ 848.988518] Buffer I/O error on dev md7, logical block 3907148544, async page read
but no error from underlying devices.
List of bad blocks:
http://sprunge.us/XSWI
What can I do now?
(loosing data from that few sectors is acceptable if the rest will be readable)
Thanks,
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
--
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 reply other threads:[~2015-12-07 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 16:05 Arkadiusz Miskiewicz [this message]
2015-12-07 16:37 ` I/O errors without erros from underlying device John Stoffel
2015-12-07 17:06 ` Arkadiusz Miskiewicz
[not found] ` <201512071803.26434.arekm@maven.pl>
2015-12-07 17:23 ` John Stoffel
2015-12-07 20:46 ` Arkadiusz Miskiewicz
2015-12-08 4:02 ` John Stoffel
2015-12-08 11:05 ` Arkadiusz Miskiewicz
2015-12-21 2:25 ` 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=201512071705.27177.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=arekm@maven.pl \
--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.