* dm-integrity
@ 2020-01-12 13:42 Gandalf Corvotempesta
2020-01-13 18:11 ` dm-integrity Song Liu
0 siblings, 1 reply; 5+ messages in thread
From: Gandalf Corvotempesta @ 2020-01-12 13:42 UTC (permalink / raw)
To: Linux RAID Mailing List
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: dm-integrity
2020-01-12 13:42 dm-integrity Gandalf Corvotempesta
@ 2020-01-13 18:11 ` Song Liu
2020-01-13 18:16 ` dm-integrity Piergiorgio Sartor
0 siblings, 1 reply; 5+ messages in thread
From: Song Liu @ 2020-01-13 18:11 UTC (permalink / raw)
To: Gandalf Corvotempesta, dm-devel; +Cc: Linux RAID Mailing List
+ 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?
Thanks,
Song
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: dm-integrity
2020-01-13 18:11 ` dm-integrity Song Liu
@ 2020-01-13 18:16 ` Piergiorgio Sartor
2020-01-13 18:58 ` dm-integrity Song Liu
0 siblings, 1 reply; 5+ messages in thread
From: Piergiorgio Sartor @ 2020-01-13 18:16 UTC (permalink / raw)
To: Song Liu; +Cc: Gandalf Corvotempesta, dm-devel, Linux RAID Mailing List
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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: dm-integrity
2020-01-13 18:16 ` dm-integrity Piergiorgio Sartor
@ 2020-01-13 18:58 ` Song Liu
2020-01-13 21:41 ` dm-integrity Gandalf Corvotempesta
0 siblings, 1 reply; 5+ messages in thread
From: Song Liu @ 2020-01-13 18:58 UTC (permalink / raw)
To: Piergiorgio Sartor
Cc: Gandalf Corvotempesta, dm-devel, Linux RAID Mailing List
On Mon, Jan 13, 2020 at 10:17 AM Piergiorgio Sartor
<piergiorgio.sartor@nexgo.de> wrote:
>
> 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.
I see. Thanks for the clarification.
>
> 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...
Right now, md_done_sync() doesn't really print any message. I think this is
easy to add. However, md check/recovery is at block granularity, so we
probably cannot print exact which sector got fixed.
Thanks,
Song
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: dm-integrity
2020-01-13 18:58 ` dm-integrity Song Liu
@ 2020-01-13 21:41 ` Gandalf Corvotempesta
0 siblings, 0 replies; 5+ messages in thread
From: Gandalf Corvotempesta @ 2020-01-13 21:41 UTC (permalink / raw)
To: Song Liu; +Cc: Piergiorgio Sartor, dm-devel, Linux RAID Mailing List
Il giorno lun 13 gen 2020 alle ore 19:58 Song Liu <song@kernel.org> ha scritto:
> Right now, md_done_sync() doesn't really print any message. I think this is
> easy to add. However, md check/recovery is at block granularity, so we
> probably cannot print exact which sector got fixed.
Well, having the exact sector fixed is not mandatory, but really useful.
Better than nothing would be md logging that has fixed "something" and
it's location (a setor, a block, ....)
9 times out of 10 the dm-integrity log would be just above the md log,
so a match between dm-integrity sector and md block would be easy,
just read the line below or above.
I think that md should be a little bit more verbose on certain
actions. (in example, saying what was fixed, the last time of scrub
and it's result, as per my previous thread and so on)
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2020-01-13 21:41 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-01-12 13:42 dm-integrity Gandalf Corvotempesta
2020-01-13 18:11 ` dm-integrity Song Liu
2020-01-13 18:16 ` dm-integrity Piergiorgio Sartor
2020-01-13 18:58 ` dm-integrity Song Liu
2020-01-13 21:41 ` dm-integrity Gandalf Corvotempesta
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox