From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: Song Liu <song@kernel.org>
Cc: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
dm-devel@redhat.com,
Linux RAID Mailing List <linux-raid@vger.kernel.org>
Subject: Re: dm-integrity
Date: Mon, 13 Jan 2020 19:16:54 +0100 [thread overview]
Message-ID: <20200113181654.GA7645@lazy.lzy> (raw)
In-Reply-To: <CAPhsuW6srGADYYD4dsUbVVBcz4bfJ-taoOy6ccpXjyU26jVTEg@mail.gmail.com>
On Mon, Jan 13, 2020 at 10:11:00AM -0800, Song Liu wrote:
> + dm-devel
>
> On Sun, Jan 12, 2020 at 5:43 AM Gandalf Corvotempesta
> <gandalf.corvotempesta@gmail.com> wrote:
> >
> > I'm testing dm-integrity.
> > Simple question: when corrupted data are found, repair is done
> > immediately or on next scrub?
> >
> > This is what I have:
> >
> > [ 6727.395808] md: data-check of RAID array md0
> > [ 6727.528589] device-mapper: integrity: Checksum failed at sector 0xe228
> > [ 6727.938689] md: md0: data-check done.
> > [ 6749.125075] md: data-check of RAID array md0
> > [ 6749.664269] md: md0: data-check done.
> >
> > if repair is done immediatly, would be possible to add a single log
> > line saying that ?
> > something like:
> > [ 6727.528589] md: md0: Repaired data at sector 0xe228
>
> I guess this belongs to dm-integrity instead of md?
Eh, well, no.
He is asking about "md" in case the underlying
layer, dm-integrity in this case, returns an error.
This could be the case also if the HDD returns
a read error which the RAID will correct and,
if I get it right, rewrite.
But I guess "md" already returns where the
correction happened, isn't like that?
I recall seeing in the logs something about
it, but it was some time ago...
bye,
--
piergiorgio
next prev parent reply other threads:[~2020-01-13 18:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-12 13:42 dm-integrity Gandalf Corvotempesta
2020-01-13 18:11 ` dm-integrity Song Liu
2020-01-13 18:16 ` Piergiorgio Sartor [this message]
2020-01-13 18:58 ` dm-integrity Song Liu
2020-01-13 21:41 ` dm-integrity Gandalf Corvotempesta
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=20200113181654.GA7645@lazy.lzy \
--to=piergiorgio.sartor@nexgo.de \
--cc=dm-devel@redhat.com \
--cc=gandalf.corvotempesta@gmail.com \
--cc=linux-raid@vger.kernel.org \
--cc=song@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