Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Thomas Glanzmann <thomas@glanzmann.de>
To: "Nicholas A. Bellinger" <nab@daterainc.com>
Cc: target-devel <target-devel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Nicholas Bellinger <nab@linux-iscsi.org>
Subject: Re: [PATCH 0/3] target: Fixes for COMPARE_AND_WRITE backend I/O failure cases
Date: Wed, 2 Oct 2013 06:31:58 +0200	[thread overview]
Message-ID: <20131002043157.GA3057@glanzmann.de> (raw)
In-Reply-To: <1380672796-437-1-git-send-email-nab@daterainc.com>

Hello Nab,

> Thomas, these are all fairly obvious fixes to me, and I've been able
> to confirm them on my setup.  Please confirm on your end, and I'll
> plan to push them for v3.12-rc4 by the end of the week.

I confirm that the fixes work. Thank you for fixing this. I did the
following:

        - Applied the patches on top of your for-next, recompiled,
          installed modules and kernel got rid of
          '/lib/modules/3.11.0-rc5+/extra/' which contained target
          modules with an unknown symbol __dynamic_pr_debug (from the
          debug build, I assume)

        - Started the target, discovered from two esx servers, created
          VMFS (no error), deployed one VM, used XCOPY to clone it three
          times, powered it on and did 4 svmotion in parallel.

So the fix works. I also have the feeling that the xcopy code became
faster, but I first have to meassure it.

I'll today some more testing with rescans from 12 ESX and svmotion
(XCOPY) of 24 VMs in parallel. But everything is looking good from my
site. I'm also working on the discovery patch.

Cheers,
        Thomas

  parent reply	other threads:[~2013-10-02  4:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02  0:13 [PATCH 0/3] target: Fixes for COMPARE_AND_WRITE backend I/O failure cases Nicholas A. Bellinger
2013-10-02  0:13 ` [PATCH 1/3] target: Reset data_length for COMPARE_AND_WRITE to NoLB * block_size Nicholas A. Bellinger
2013-10-02  0:13 ` [PATCH 2/3] target: Fix recursive COMPARE_AND_WRITE callback failure Nicholas A. Bellinger
2013-10-02  0:13 ` [PATCH 3/3] target: Fail on non zero scsi_status in compare_and_write_callback Nicholas A. Bellinger
2013-10-02  4:31 ` Thomas Glanzmann [this message]
2013-10-02  5:17   ` [PATCH 0/3] target: Fixes for COMPARE_AND_WRITE backend I/O failure cases Nicholas A. Bellinger
2013-10-03 11:38     ` Thomas Glanzmann
2013-10-03 12:14       ` Nicholas A. Bellinger

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=20131002043157.GA3057@glanzmann.de \
    --to=thomas@glanzmann.de \
    --cc=linux-scsi@vger.kernel.org \
    --cc=nab@daterainc.com \
    --cc=nab@linux-iscsi.org \
    --cc=target-devel@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