All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: Radha Ramachandran <radha@google.com>
Cc: fio@vger.kernel.org
Subject: Re: Verify pattern & header meta data
Date: Mon, 27 Jul 2009 12:28:41 +0200	[thread overview]
Message-ID: <20090727102841.GB4148@kernel.dk> (raw)
In-Reply-To: <66dfd3fe0907231233u53c30fe7l20c4b1103459292c@mail.gmail.com>

On Thu, Jul 23 2009, Radha Ramachandran wrote:
> Hi,
> Is there any reason why during the verify phase, when the pattern
> verification is on, there is no meta verification done. I see why
> doing pattern verify followed by a crc/md5/sha verification can be
> redundant, but I think it is useful to have meta verify check even if
> there is pattern verification just to confirm that the data was read
> from the correct location as expected.
> If this is reasonable I have a change to check meta data after pattern
> verification where applicable:
> 
> 
> >git diff
> diff --git a/verify.c b/verify.c
> index 84fc015..3c8997a 100644
> --- a/verify.c
> +++ b/verify.c
> @@ -482,6 +482,12 @@ int verify_io_u(struct thread_data *td, struct io_u *io_u)
>                                 log_err("fio: verify failed at %llu/%u\n",
>                                         io_u->offset + hdr_num * hdr->len,
>                                         hdr->len);
> +                       /*
> +                        * Also verify the meta data if applicable.
> +                        */
> +                       if (hdr->verify_type == VERIFY_META) {
> +                               ret = ret | verify_io_u_meta(hdr, td,
> io_u, hdr_num);
> +                       }
>                         continue;
>                 }

It looks like an oversight, I've added your patch. Thanks!

-- 
Jens Axboe


      reply	other threads:[~2009-07-27 10:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-23 19:33 Verify pattern & header meta data Radha Ramachandran
2009-07-27 10:28 ` Jens Axboe [this message]

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=20090727102841.GB4148@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=fio@vger.kernel.org \
    --cc=radha@google.com \
    /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.