From: Salatiel Filho <salatiel.filho@gmail.com>
To: John Stoffel <john@stoffel.org>
Cc: linux-raid@vger.kernel.org
Subject: Re: Input/Output error reading from a clean raid
Date: Mon, 23 Jan 2017 11:42:04 -0300 [thread overview]
Message-ID: <CAGmni9qwyHo+G8e4APF99Ai-N_d5WfOhkT0xLoq-8tVkTOjonA@mail.gmail.com> (raw)
In-Reply-To: <22661.19403.314279.130591@quad.stoffel.home>
The output of the command is:
# dd if=Fotos.zip of=/dev/null
dd: error reading ‘Fotos.zip’: Input/output error
328704+0 records in
328704+0 records out
168296448 bytes (168 MB) copied, 0.127723 s, 1.3 GB/s
or
# cp Fotos.zip /tmp/
cp: error reading ‘Fotos.zip’: Input/output error
cp: failed to extend ‘/tmp/Fotos.zip’: Input/output error
There is nothing on dmesg after running those commands;
[]'s
Salatiel
On Sun, Jan 22, 2017 at 9:18 PM, John Stoffel <john@stoffel.org> wrote:
>
> Salatiel> I am trying to recover a few files from my backup. The
> Salatiel> backup is on a raid 5 + ext4. There are several files where
> Salatiel> i get I/O error. The raid appears to be clean and fsck shows
> Salatiel> no errors. Any ideas what could it be ?
>
> Salatiel> md1 : active raid5 sdd1[0] sdg1[4] sdf1[2] sde1[1]
> Salatiel> 3220829184 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
> Salatiel> bitmap: 1/8 pages [4KB], 65536KB chunk
>
> It would help if you could post the error(s) you're getting, along
> with any output from dmesg during that time. Have you done a full
> scan of the disk looking for errors? You might just have silent
> read errors in your array. So as root do:
>
> # echo check >>/sys/block/md??/md/sync_action
>
> where md?? is the name of your md array you want to check. You can
> get the name from:
>
> cat /proc/mdstat
>
> and of course it would help to post that info as well if you want more
> help.
>
> John
next prev parent reply other threads:[~2017-01-23 14:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 14:08 Input/Output error reading from a clean raid Salatiel Filho
2017-01-23 0:18 ` John Stoffel
2017-01-23 14:42 ` Salatiel Filho [this message]
2017-01-23 16:12 ` John Stoffel
[not found] ` <20170123010334.GA7546@metamorpher.de>
2017-01-23 14:02 ` Salatiel Filho
2017-01-23 17:07 ` John Stoffel
2017-01-23 17:23 ` Wols Lists
2017-01-23 17:34 ` Andreas Klauer
2017-01-24 21:15 ` Salatiel Filho
2017-01-24 21:58 ` Wols Lists
2017-01-25 15:54 ` John Stoffel
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=CAGmni9qwyHo+G8e4APF99Ai-N_d5WfOhkT0xLoq-8tVkTOjonA@mail.gmail.com \
--to=salatiel.filho@gmail.com \
--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 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.