From owner-freebsd-bugs@freebsd.org Sun Jul 24 20:13:22 2016 Return-Path: Delivered-To: freebsd-bugs@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 E55B4BA336E for ; Sun, 24 Jul 2016 20:13:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (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 D4992185B for ; Sun, 24 Jul 2016 20:13:22 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id u6OKDMi3042443 for ; Sun, 24 Jul 2016 20:13:22 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 211028] [GEOM][Hyper-V] gpart can't detect the new free space after the disk capacity changes Date: Sun, 24 Jul 2016 20:13:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: peter@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Jul 2016 20:13:23 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D211028 --- Comment #31 from Peter Wemm --- The first few boot attempts looked like this: ... (da0:mpt0:0:0:0): UNMAPPED (da1:mpt0:0:1:0): da0 at mpt0 bus 0 scbus0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: Serial Number A107P49025GU da0: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da0: Command Queueing enabled da0: 70007MB (143374650 512 byte sectors) da0: Delete methods: ses0: Nfans 0 Npwr 0 Nslots 6 Lck 0 Ntherm 0 Nspkrs 0 Ntstats 0 UNMAPPED (da2:mpt0:0:2:0): UNMAPPED (da3:mpt0:0:3:0): UNMAPPED (da4:mpt0:0:4:0): UNMAPPED (da5:mpt0:0:5:GEOM: new disk da0 (73407820800 bytes) GEOM: new disk da1 (0 bytes) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ GEOM: new disk da2 (0 bytes) da3 at mpt0 bus 0 scbus0 target 3 lun 0 da3: Fixed Direct Access SCSI-3 device da3: Serial Number A107P49025H7 da3: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da3: Command Queueing enabled da3: 70007MB (143374650 512 byte sectors) da3: Delete methods: da2 at mpt0 bus 0 scbus0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: Serial Number A107P49025GB da2: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da2: Command Queueing enabled da2: 70007MB (143374650 512 byte sectors) da2: Delete methods: da1 at mpt0 bus 0 scbus0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: Serial Number A107P49025H2 da1: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da1: Command Queueing enabled da1: 70007MB (143374650 512 byte sectors) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ da1: Delete methods: da4 at mpt0 bus 0 scbus0 target 4 lun 0 da4: Fixed Direct Access SCSI-3 device da4: Serial Number C80666ZK da4: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da4: Command Queueing enabled da4: 70007MB (143374650 512 byte sectors) da4: Delete methods: GEOM: new disk da3 (73407820800 bytes) GEOM: new disk da4 (73407820800 bytes) 0): UNMAPPED pass0 at mpt0 bus 0 scbus0 target 0 lun 0 da5 at mpt0 bus 0 scbus0 target 5 lun 0 da5: Fixed Direct Access SCSI-3 device da5: Serial Number A107P49025GP da5: 320.000MB/s transfers (160.000MHz, offset 127, 16bit) da5: Command Queueing enabled da5: 70007MB (143374650 512 byte sectors) da5: Delete methods: ... Note the "GEOM new disk, 0 bytes" happens before the probe messages.=20 Presumably the nature of the original panic we were seeing was that was try= ing to resize an uninitialized disk. It no longer detects the corrupt GPT but no longer panics either. The machine in question is slow to boot, but I'll try a few more iterations. --=20 You are receiving this mail because: You are the assignee for the bug.=