From: Arkadiusz Miskiewicz <a.miskiewicz@gmail.com>
To: John Stoffel <john@stoffel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: I/O errors without erros from underlying device
Date: Mon, 7 Dec 2015 18:06:15 +0100 [thread overview]
Message-ID: <201512071806.15970.a.miskiewicz@gmail.com> (raw)
In-Reply-To: <22117.46523.245486.830064@quad.stoffel.home>
On Monday 07 of December 2015, John Stoffel wrote:
> Arkadiusz> 4.3.0 kernel, raid6 array:
>
> I think there's a bug in the 4.3.x and 4.4-rc3 and lower with block
> merges. I ran into these over the weekend, where v4.2.6 was stable,
> but anything higher would lock up and crash on me.
Well, no crashes here.
> So first step would be to make sure you get and test v4.4-rc4.
Do you know which commit there?
>
> Arkadiusz> md7 : active raid6 sdg[10] sdad1[9] sdac1[8] sdag1[7] sdaf1[6]
> sdae1[5] sdaj1[4] sdai1[3] sdah1[2] sdn1[1] Arkadiusz> 31255089152
> blocks super 1.2 level 6, 512k chunk, algorithm 2 [10/10] [UUUUUUUUUU]
> Arkadiusz> bitmap: 1/30 pages [4KB], 65536KB chunk
>
> Arkadiusz> array had weird failure where many disks went into failed state
> but Arkadiusz> remove && adding these disks "fixed" it (turns out not
> really fixed it).
>
> Arkadiusz> Unfortunately now some reads fail:
>
> Arkadiusz> pread(4, 0x1483a00, 4096, 16003680464896) = -1 EIO (Input/output
> error)
>
> Arkadiusz> To reproduce used xfs_io
> Arkadiusz> xfs_io -d -c "pread 16003680464896 4096" /dev/md7
> Arkadiusz> pread64: Input/output error
> Arkadiusz> which does pread exactly as shown above.
>
> Arkadiusz> write also fails for that area:
> Arkadiusz> xfs_io -d -c "pwrite 16003680464896 4096" /dev/md7
> Arkadiusz> pwrite64: Input/output error
>
> Arkadiusz> Note that nothing is written in dmesg when that happens.
>
> Arkadiusz> I've tried various offsets and sizes of pread and at some point
> that was logged: Arkadiusz> [ 848.988518] Buffer I/O error on dev md7,
> logical block 3907148544, async page read
>
> Arkadiusz> but no error from underlying devices.
>
> Arkadiusz> List of bad blocks:
> Arkadiusz> http://sprunge.us/XSWI
>
> Arkadiusz> What can I do now?
>
> Arkadiusz> (loosing data from that few sectors is acceptable if the rest
> will be readable)
>
> Arkadiusz> Thanks,
> Arkadiusz> --
> Arkadiusz> Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
> Arkadiusz> --
> Arkadiusz> To unsubscribe from this list: send the line "unsubscribe
> linux-raid" in Arkadiusz> the body of a message to
> majordomo@vger.kernel.org
> Arkadiusz> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
--
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 prev parent reply other threads:[~2015-12-07 17:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 16:05 I/O errors without erros from underlying device Arkadiusz Miskiewicz
2015-12-07 16:37 ` John Stoffel
2015-12-07 17:06 ` Arkadiusz Miskiewicz [this message]
[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=201512071806.15970.a.miskiewicz@gmail.com \
--to=a.miskiewicz@gmail.com \
--cc=arekm@maven.pl \
--cc=john@stoffel.org \
--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).