From owner-freebsd-stable@freebsd.org  Thu Jun 29 14:11:05 2017
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 295C5D9E675
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Thu, 29 Jun 2017 14:11:05 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3])
 by mx1.freebsd.org (Postfix) with ESMTP id 162BD12ED
 for <freebsd-stable@freebsd.org>; Thu, 29 Jun 2017 14:11:05 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: by mailman.ysv.freebsd.org (Postfix)
 id 123ACD9E673; Thu, 29 Jun 2017 14:11:05 +0000 (UTC)
Delivered-To: stable@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 11CA8D9E670
 for <stable@mailman.ysv.freebsd.org>; Thu, 29 Jun 2017 14:11:05 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from constantine.ingresso.co.uk (unknown [IPv6:2a02:b90:3002:411::3])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D53C112EC
 for <stable@freebsd.org>; Thu, 29 Jun 2017 14:11:04 +0000 (UTC)
 (envelope-from petefrench@ingresso.co.uk)
Received: from dilbert.ingresso.co.uk ([2a02:b90:3002:411::6])
 by constantine.ingresso.co.uk with esmtpsa
 (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD))
 (envelope-from <petefrench@ingresso.co.uk>) id 1dQa9u-000CSp-3o
 for stable@freebsd.org; Thu, 29 Jun 2017 14:11:02 +0000
Received: from petefrench by dilbert.ingresso.co.uk with local (Exim 4.89
 (FreeBSD)) (envelope-from <petefrench@ingresso.co.uk>)
 id 1dQa9t-00053N-WC
 for stable@freebsd.org; Thu, 29 Jun 2017 15:11:02 +0100
To: stable@freebsd.org
Subject: Problems attaching disks in Azure under 11.1-BETA2
Message-Id: <E1dQa9t-00053N-WC@dilbert.ingresso.co.uk>
From: Pete French <petefrench@ingresso.co.uk>
Date: Thu, 29 Jun 2017 15:11:01 +0100
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jun 2017 14:11:05 -0000

I am trying to attach a brand new disk to an azure VM, and
what I see is the disk attachng and detaching immediately like this:

	da2 at storvsc3 bus 0 scbus5 target 0 lun 0
	da2: <Msft Virtual Disk 1.0> Fixed Direct Access SPC-2 SCSI device
	da2: 300.000MB/s transfers
	da2: Command Queueing enabled
	da2: 32768MB (67108864 512 byte sectors)
	da2 at storvsc3 bus 0 scbus5 target 0 lun 0
	da2: <Msft Virtual Disk 1.0> detached
	g_access(918): provider da2 has error
	g_access(918): provider da2 has error
	g_access(918): provider da2 has error
	g_access(918): provider da2 has error
	(da2:storvsc3:0:0:0): Periph destroyed

I have seen this before with an existing disk if I detahc and reattach
wiht a new LUN numer, but never with a brand new disk. The command I
am using to create this is below:

	az vm disk attach --vm-name az-london01 \
		--resource-group ticketswitch-london \
		--caching ReadWrite --new --size-gb 32 \
		--sku Standard_LRS \
		--disk az-london01-tank01

The only thing I could find in bug reports which is similar is this:

	https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212914

But those patches should have gone in ages ago. Will try and find a
workaround for now, but its a bit puzzling.

-pete.